Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d791e71266ff8f445575d13f62f5e6a85ff9c7fa46fced0ee484d3a381847854

Tx prefix hash: a3ac987f9526a51a85a3a658e50138482acf72e9d18908494c8a40e64d11c0b4
Tx public key: 297113aef149bfc0e6ba208fc99607427782f138cc5b15b1d97c25fb9a9d54a7
Timestamp: 1717500273 Timestamp [UCT]: 2024-06-04 11:24:33 Age [y:d:h:m:s]: 00:337:19:28:14
Block: 1036846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241435 RingCT/type: yes/0
Extra: 01297113aef149bfc0e6ba208fc99607427782f138cc5b15b1d97c25fb9a9d54a70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f70631a0d6d3c7135790c765d57726a9f0c55d7ce8a5889ad435c2a869523f72 0.600000000000 1505375 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": 1036856, "vin": [ { "gen": { "height": 1036846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f70631a0d6d3c7135790c765d57726a9f0c55d7ce8a5889ad435c2a869523f72" } } ], "extra": [ 1, 41, 113, 19, 174, 241, 73, 191, 192, 230, 186, 32, 143, 201, 150, 7, 66, 119, 130, 241, 56, 204, 91, 21, 177, 217, 124, 37, 251, 154, 157, 84, 167, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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