Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ffcd95e1ba2c59cfad367d4d66c53d22eca57c3a95e558894d1db0633458dce

Tx prefix hash: 75c34e89c65600f531de1a744f6c3c8de8648e12ddd6db6fbb2af9868e4a1115
Tx public key: 88376a2920ee7195dadd0399eab8d8ef4c167bcd7953ca2c46e777c6eb91fc77
Timestamp: 1697431290 Timestamp [UCT]: 2023-10-16 04:41:30 Age [y:d:h:m:s]: 01:095:18:08:48
Block: 870652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329655 RingCT/type: yes/0
Extra: 0188376a2920ee7195dadd0399eab8d8ef4c167bcd7953ca2c46e777c6eb91fc7702110000000533af99f4000000000000000000

1 output(s) for total of 0.800144686000 dcy

stealth address amount amount idx
00: 223a420c38a1d2e355235bf36dff82359b61f692a51ab10b6dbb080f1e82afc2 0.800144686000 1325535 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": 870662, "vin": [ { "gen": { "height": 870652 } } ], "vout": [ { "amount": 800144686, "target": { "key": "223a420c38a1d2e355235bf36dff82359b61f692a51ab10b6dbb080f1e82afc2" } } ], "extra": [ 1, 136, 55, 106, 41, 32, 238, 113, 149, 218, 221, 3, 153, 234, 184, 216, 239, 76, 22, 123, 205, 121, 83, 202, 44, 70, 231, 119, 198, 235, 145, 252, 119, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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