Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 886bd2f83879296a14302d4c06ca88ef9a2ed2d1d685a0436ea132f20d04f87e

Tx prefix hash: 22f478d4192fe3f598022f154fd54aca1fc59c2683ba5d8c916753996fcfba0c
Tx public key: 4d7e086881373e7e9af4232cada7d8fce200f3c65a1af482ee7b98de7593fd88
Timestamp: 1717741170 Timestamp [UCT]: 2024-06-07 06:19:30 Age [y:d:h:m:s]: 00:178:05:26:56
Block: 1038838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127552 RingCT/type: yes/0
Extra: 014d7e086881373e7e9af4232cada7d8fce200f3c65a1af482ee7b98de7593fd880211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b770c4261e46ec21fa5891a1b0bccb4f981d1b255a0fbc39c73e9b866f9d52b 0.600000000000 1507399 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": 1038848, "vin": [ { "gen": { "height": 1038838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b770c4261e46ec21fa5891a1b0bccb4f981d1b255a0fbc39c73e9b866f9d52b" } } ], "extra": [ 1, 77, 126, 8, 104, 129, 55, 62, 126, 154, 244, 35, 44, 173, 167, 216, 252, 226, 0, 243, 198, 90, 26, 244, 130, 238, 123, 152, 222, 117, 147, 253, 136, 2, 17, 0, 0, 0, 8, 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