Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 885a681a1a28873fbdb824ec019e80c10f24fce360be54bbc3d162721fb7a91b

Tx prefix hash: 215559bbc5bcdee207ea984421fd380315ab178f01cf031cda0aa2757e9b26ea
Tx public key: b8aec3e5b0b6333d9a50139fa5e9c3b57e19b7502d2c7746737487da4021dd76
Timestamp: 1634281950 Timestamp [UCT]: 2021-10-15 07:12:30 Age [y:d:h:m:s]: 03:042:14:06:08
Block: 353408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 808256 RingCT/type: yes/0
Extra: 01b8aec3e5b0b6333d9a50139fa5e9c3b57e19b7502d2c7746737487da4021dd760211000000095d7cc334000000000000000000

1 output(s) for total of 41.401207510000 dcy

stealth address amount amount idx
00: 9397845ea2308f2abd6b3e250261c6fceaea1f59fd1b7e3e13f23f6cea3cb324 41.401207510000 722174 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": 353418, "vin": [ { "gen": { "height": 353408 } } ], "vout": [ { "amount": 41401207510, "target": { "key": "9397845ea2308f2abd6b3e250261c6fceaea1f59fd1b7e3e13f23f6cea3cb324" } } ], "extra": [ 1, 184, 174, 195, 229, 176, 182, 51, 61, 154, 80, 19, 159, 165, 233, 195, 181, 126, 25, 183, 80, 45, 44, 119, 70, 115, 116, 135, 218, 64, 33, 221, 118, 2, 17, 0, 0, 0, 9, 93, 124, 195, 52, 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