Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34434cd3a9c89408c75f0dac185ec05b2ea4e34775d5be15b5313feca4dea602

Tx prefix hash: c8e8d4f7cd8de91c95cf779ede29c0b87bf912be83881c91ab20781a7977a768
Tx public key: 6fcdcfc266b60485af2de3461ab706e1df6b82b5a4ab413e3d307b01e52c799c
Timestamp: 1705941765 Timestamp [UCT]: 2024-01-22 16:42:45 Age [y:d:h:m:s]: 01:291:20:12:08
Block: 940967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467408 RingCT/type: yes/0
Extra: 016fcdcfc266b60485af2de3461ab706e1df6b82b5a4ab413e3d307b01e52c799c02110000000158e72c11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21a004a7fb6429030cef0d385901e9de78b40c4489653726d31055ff249acc1e 0.600000000000 1399109 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": 940977, "vin": [ { "gen": { "height": 940967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21a004a7fb6429030cef0d385901e9de78b40c4489653726d31055ff249acc1e" } } ], "extra": [ 1, 111, 205, 207, 194, 102, 182, 4, 133, 175, 45, 227, 70, 26, 183, 6, 225, 223, 107, 130, 181, 164, 171, 65, 62, 61, 48, 123, 1, 229, 44, 121, 156, 2, 17, 0, 0, 0, 1, 88, 231, 44, 17, 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