Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdb889a4659c9de06879d59bc010704f3dec94f83b541238e78e215add201b16

Tx prefix hash: 8416dc9dbbe82f0abbc13f6deb499d038a07658038720d0312a5cdcdeb640bfe
Tx public key: 3aa6bd320caf5cae82f722abdbe95ec3959ab1f806f4088239f06f15f5a4dd7b
Timestamp: 1700688579 Timestamp [UCT]: 2023-11-22 21:29:39 Age [y:d:h:m:s]: 01:126:20:58:47
Block: 897448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351848 RingCT/type: yes/0
Extra: 013aa6bd320caf5cae82f722abdbe95ec3959ab1f806f4088239f06f15f5a4dd7b02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.652202133000 dcy

stealth address amount amount idx
00: ef53b9e911b3a3f5d57e932657e070cb0269055c75973944a3f0ffc70770f403 0.652202133000 1353823 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": 897458, "vin": [ { "gen": { "height": 897448 } } ], "vout": [ { "amount": 652202133, "target": { "key": "ef53b9e911b3a3f5d57e932657e070cb0269055c75973944a3f0ffc70770f403" } } ], "extra": [ 1, 58, 166, 189, 50, 12, 175, 92, 174, 130, 247, 34, 171, 219, 233, 94, 195, 149, 154, 177, 248, 6, 244, 8, 130, 57, 240, 111, 21, 245, 164, 221, 123, 2, 17, 0, 0, 0, 1, 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