Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a0906fe368210e5219c281d66387b0b1fda5bb054369d0be3fe9f0ccf305f1

Tx prefix hash: de7476776606af3e03ec97173d08e793ba873cc7b64fd1c204671c7f13c4719d
Tx public key: 349b3d6239172fd8211330aa9e2cda2654de5b439907b0f3ce28bd19c8a1035e
Timestamp: 1706501101 Timestamp [UCT]: 2024-01-29 04:05:01 Age [y:d:h:m:s]: 01:308:03:01:04
Block: 945621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479052 RingCT/type: yes/0
Extra: 01349b3d6239172fd8211330aa9e2cda2654de5b439907b0f3ce28bd19c8a1035e0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bb574846e35a04cacd4c4bb9fc1fcdc36e485a964950211955a583c8bd7690e 0.600000000000 1403937 of 15

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": 945631, "vin": [ { "gen": { "height": 945621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bb574846e35a04cacd4c4bb9fc1fcdc36e485a964950211955a583c8bd7690e" } } ], "extra": [ 1, 52, 155, 61, 98, 57, 23, 47, 216, 33, 19, 48, 170, 158, 44, 218, 38, 84, 222, 91, 67, 153, 7, 176, 243, 206, 40, 189, 25, 200, 161, 3, 94, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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