Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b2e2b293e6838a27d093d924a5a08ea4b31ab73d0d63f7c669f96c90e102ce36

Tx prefix hash: 989a570f887a5daeac43f1280dea8fb8dac4d2f578a9a0b5e1bcae36b83f3d4d
Tx public key: 2220001e09f040c0e1cf25c7654a2502d71be242fde1ec9226a46f5d9d9c145a
Timestamp: 1745922341 Timestamp [UCT]: 2025-04-29 10:25:41 Age [y:d:h:m:s]: 00:276:17:51:23
Block: 1271960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195408 RingCT/type: yes/0
Extra: 012220001e09f040c0e1cf25c7654a2502d71be242fde1ec9226a46f5d9d9c145a02110000000e1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5519afb0cec583ac4c4c1e6345e904d62e7e18a4588622c00ed6774b356d06 0.600000000000 1759231 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1271970, "vin": [ { "gen": { "height": 1271960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5519afb0cec583ac4c4c1e6345e904d62e7e18a4588622c00ed6774b356d06" } } ], "extra": [ 1, 34, 32, 0, 30, 9, 240, 64, 192, 225, 207, 37, 199, 101, 74, 37, 2, 215, 27, 226, 66, 253, 225, 236, 146, 38, 164, 111, 93, 157, 156, 20, 90, 2, 17, 0, 0, 0, 14, 31, 144, 81, 122, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8