Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f200cdf2d302b1f101c50732085e4717cb15e18942c6e659e0454e3532b4e6

Tx prefix hash: 29d22b468a5a7ce25ceb95c7ab13bb154bb2f6ccf3135dbfd5c1afc66ede9eeb
Tx public key: 57bbabf11e61651e3480eb80da1d67d63e9d4d1b2c436d5966f6f6747ffff6a6
Timestamp: 1701359825 Timestamp [UCT]: 2023-11-30 15:57:05 Age [y:d:h:m:s]: 01:129:09:01:37
Block: 903012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353613 RingCT/type: yes/0
Extra: 0157bbabf11e61651e3480eb80da1d67d63e9d4d1b2c436d5966f6f6747ffff6a602110000000675e3f0e9000000000000000000

1 output(s) for total of 0.625095489000 dcy

stealth address amount amount idx
00: 35fd643a5f6086d23ce5f315a6b0f4f9a5c188d7fb261c0b72fd8bee933d7811 0.625095489000 1359677 of 0

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": 903022, "vin": [ { "gen": { "height": 903012 } } ], "vout": [ { "amount": 625095489, "target": { "key": "35fd643a5f6086d23ce5f315a6b0f4f9a5c188d7fb261c0b72fd8bee933d7811" } } ], "extra": [ 1, 87, 187, 171, 241, 30, 97, 101, 30, 52, 128, 235, 128, 218, 29, 103, 214, 62, 157, 77, 27, 44, 67, 109, 89, 102, 246, 246, 116, 127, 255, 246, 166, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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