Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb91c3a54a089bda298f31b00f5ed348bf152ca2b5d69ecb2a75259e9a577435

Tx prefix hash: 4074a004d6e9cdc11e6936f21d74bc00c2669bbe608aa1ba52d3aaec26923d29
Tx public key: b2d3dc3d937155aa12059f867aebf9bc2a9b4a61e706df4151a9e87f80377756
Timestamp: 1759240103 Timestamp [UCT]: 2025-09-30 13:48:23 Age [y:d:h:m:s]: 00:052:10:33:12
Block: 1379758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37547 RingCT/type: yes/0
Extra: 01b2d3dc3d937155aa12059f867aebf9bc2a9b4a61e706df4151a9e87f8037775602110000000697baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45a307167f62b9198e290bcc076c8474ea43da6aa6fb6491061de2bc9001f133 0.600000000000 1867865 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": 1379768, "vin": [ { "gen": { "height": 1379758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45a307167f62b9198e290bcc076c8474ea43da6aa6fb6491061de2bc9001f133" } } ], "extra": [ 1, 178, 211, 220, 61, 147, 113, 85, 170, 18, 5, 159, 134, 122, 235, 249, 188, 42, 155, 74, 97, 231, 6, 223, 65, 81, 169, 232, 127, 128, 55, 119, 86, 2, 17, 0, 0, 0, 6, 151, 186, 249, 34, 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