Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b24a03bda9364a7ff2c6fc5cbeaaec4f239bad40d8390d0ff3bc38a06ea22f1a

Tx prefix hash: 7fde45a8f4da38b0b7f4f957657d38252f30d1ae58989f87b59ea4cd207aed91
Tx public key: 33631efc405dd0600b2781f46e131ef590cdf6bf4811422fc2746128e8dd9c8e
Timestamp: 1712599225 Timestamp [UCT]: 2024-04-08 18:00:25 Age [y:d:h:m:s]: 00:319:23:45:28
Block: 996164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228772 RingCT/type: yes/0
Extra: 0133631efc405dd0600b2781f46e131ef590cdf6bf4811422fc2746128e8dd9c8e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8818b1ab71088270ca781a43f2d2f0a3c8263ea2dd82d488958fb5c54367fd8 0.600000000000 1456580 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": 996174, "vin": [ { "gen": { "height": 996164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8818b1ab71088270ca781a43f2d2f0a3c8263ea2dd82d488958fb5c54367fd8" } } ], "extra": [ 1, 51, 99, 30, 252, 64, 93, 208, 96, 11, 39, 129, 244, 110, 19, 30, 245, 144, 205, 246, 191, 72, 17, 66, 47, 194, 116, 97, 40, 232, 221, 156, 142, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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