Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d7ce46e32ef7a63e91f59b6e371e7954ec170174cafdcc895e8d948f10c5a0

Tx prefix hash: 2f8ab1d747311c7362f24571e7940a06f4a62a5e9c9a8733eb679179a621faca
Tx public key: b2c071620497202f79d16e3d4255d6b796059c9e4e88b6145e037678f292cb6e
Timestamp: 1712621414 Timestamp [UCT]: 2024-04-09 00:10:14 Age [y:d:h:m:s]: 00:322:11:46:47
Block: 996351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230565 RingCT/type: yes/0
Extra: 01b2c071620497202f79d16e3d4255d6b796059c9e4e88b6145e037678f292cb6e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdacc5ba308567e93300d6344d249a4dd186d06862514d53db594d5160234035 0.600000000000 1456769 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": 996361, "vin": [ { "gen": { "height": 996351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdacc5ba308567e93300d6344d249a4dd186d06862514d53db594d5160234035" } } ], "extra": [ 1, 178, 192, 113, 98, 4, 151, 32, 47, 121, 209, 110, 61, 66, 85, 214, 183, 150, 5, 156, 158, 78, 136, 182, 20, 94, 3, 118, 120, 242, 146, 203, 110, 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