Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 665ebe82b5b7f640cd8a689f2508aa640148b618dad826a50c04f3cba72c918b

Tx prefix hash: 76f6725a140a6348939419323bca493d70024930e26d352122d165e53b19ac6a
Tx public key: 35076c72b3edf01b3d81a3cbe3ee6b3d7f7f2acdf0cbdcf3df5cf846b658208b
Timestamp: 1698940231 Timestamp [UCT]: 2023-11-02 15:50:31 Age [y:d:h:m:s]: 01:139:11:49:50
Block: 883162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360706 RingCT/type: yes/0
Extra: 0135076c72b3edf01b3d81a3cbe3ee6b3d7f7f2acdf0cbdcf3df5cf846b658208b02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.727306860000 dcy

stealth address amount amount idx
00: 11f8ee29ffad266c53cc506d7b983ec5500a824fe95043e992d344a7e2063e3a 0.727306860000 1338850 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": 883172, "vin": [ { "gen": { "height": 883162 } } ], "vout": [ { "amount": 727306860, "target": { "key": "11f8ee29ffad266c53cc506d7b983ec5500a824fe95043e992d344a7e2063e3a" } } ], "extra": [ 1, 53, 7, 108, 114, 179, 237, 240, 27, 61, 129, 163, 203, 227, 238, 107, 61, 127, 127, 42, 205, 240, 203, 220, 243, 223, 92, 248, 70, 182, 88, 32, 139, 2, 17, 0, 0, 0, 2, 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