Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 749d1ed6d4d0c2612c2d0f404ac24cb135ca803edd0b8465c964f3088d84f1d2

Tx prefix hash: b746f9ead0a600d7884673f46b12b0deae0288ecfec7f92e00d258ca9b10cc07
Tx public key: 5655fa9bd93280dadb54345116e6142dcf770efa91686c18f48ce86ef1dc3e8a
Timestamp: 1737180853 Timestamp [UCT]: 2025-01-18 06:14:13 Age [y:d:h:m:s]: 00:059:01:30:42
Block: 1199847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41981 RingCT/type: yes/0
Extra: 015655fa9bd93280dadb54345116e6142dcf770efa91686c18f48ce86ef1dc3e8a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8e6c15b454b67b3a2df88d9d757e64bdfbd3e08f6b8814eef5c53b5b2404c42 0.600000000000 1686480 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": 1199857, "vin": [ { "gen": { "height": 1199847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8e6c15b454b67b3a2df88d9d757e64bdfbd3e08f6b8814eef5c53b5b2404c42" } } ], "extra": [ 1, 86, 85, 250, 155, 217, 50, 128, 218, 219, 84, 52, 81, 22, 230, 20, 45, 207, 119, 14, 250, 145, 104, 108, 24, 244, 140, 232, 110, 241, 220, 62, 138, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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