Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b2d2e738552a0ecbdd5e505fbec8b7843f5228464dae20f89db329956d28d68

Tx prefix hash: e83c3dceb46ddf3a0f986183f9db2b40634fd1ef1c45e712e22703f4aa2bd92e
Tx public key: 61c2005d2970632c761720684120c8bdb4b56b1ffc46da817951a5a17d0dde53
Timestamp: 1681725305 Timestamp [UCT]: 2023-04-17 09:55:05 Age [y:d:h:m:s]: 01:271:00:53:48
Block: 740477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455218 RingCT/type: yes/0
Extra: 0161c2005d2970632c761720684120c8bdb4b56b1ffc46da817951a5a17d0dde530211000000035029cbac000000000000000000

1 output(s) for total of 2.160192876000 dcy

stealth address amount amount idx
00: 0a847d77b8e17a7c5b83af6327183f323e03d882b0f02ea16252f05707c2b2b6 2.160192876000 1187372 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": 740487, "vin": [ { "gen": { "height": 740477 } } ], "vout": [ { "amount": 2160192876, "target": { "key": "0a847d77b8e17a7c5b83af6327183f323e03d882b0f02ea16252f05707c2b2b6" } } ], "extra": [ 1, 97, 194, 0, 93, 41, 112, 99, 44, 118, 23, 32, 104, 65, 32, 200, 189, 180, 181, 107, 31, 252, 70, 218, 129, 121, 81, 165, 161, 125, 13, 222, 83, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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