Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31f164ed7d0bc864c6db75bcb0dc4ddccb5b72492347df5015a714d1de30874f

Tx prefix hash: b857eea2cb250b8df4258f161e40b8a47f9cbebc1679fad76240abb6660c16b6
Tx public key: 563927449869f04fd6f6e6c99c9931eaf43bf9edf0f060f7d5308c3320d0ee0e
Timestamp: 1722952447 Timestamp [UCT]: 2024-08-06 13:54:07 Age [y:d:h:m:s]: 00:234:05:24:52
Block: 1082028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167294 RingCT/type: yes/0
Extra: 01563927449869f04fd6f6e6c99c9931eaf43bf9edf0f060f7d5308c3320d0ee0e02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5431988ebbc21902504a39b3d7a911d9d21a96fff590dc1c9453875837573158 0.600000000000 1555851 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": 1082038, "vin": [ { "gen": { "height": 1082028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5431988ebbc21902504a39b3d7a911d9d21a96fff590dc1c9453875837573158" } } ], "extra": [ 1, 86, 57, 39, 68, 152, 105, 240, 79, 214, 246, 230, 201, 156, 153, 49, 234, 244, 59, 249, 237, 240, 240, 96, 247, 213, 48, 140, 51, 32, 208, 238, 14, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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