Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: decc4d50d27f5cb67a5bcfee95823e8c14e84ae867039bf2186014753b99b358

Tx prefix hash: bc653f48bc44096f19b20bd3e49f0df75fedb1e703a627739375ec06137e5b7c
Tx public key: 0ce2259b43c6bd3d72315f6a52cdcf0f625f650fa80e257756d28dd524dee4f6
Timestamp: 1733690528 Timestamp [UCT]: 2024-12-08 20:42:08 Age [y:d:h:m:s]: 00:149:02:14:29
Block: 1170975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106352 RingCT/type: yes/0
Extra: 010ce2259b43c6bd3d72315f6a52cdcf0f625f650fa80e257756d28dd524dee4f6021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 960671647c54e9cb2134381b87f9291013d77470dece8e78d3cd7922cb662458 0.600000000000 1656710 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": 1170985, "vin": [ { "gen": { "height": 1170975 } } ], "vout": [ { "amount": 600000000, "target": { "key": "960671647c54e9cb2134381b87f9291013d77470dece8e78d3cd7922cb662458" } } ], "extra": [ 1, 12, 226, 37, 155, 67, 198, 189, 61, 114, 49, 95, 106, 82, 205, 207, 15, 98, 95, 101, 15, 168, 14, 37, 119, 86, 210, 141, 213, 36, 222, 228, 246, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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