Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4be1a1bdf378590730dae0e21e037b35b2050d787615210df699181f3fcdc83

Tx prefix hash: 51e0e23b11120ec6ae43fc37aa530843455d0af9a9c1a7649855946689d3574d
Tx public key: 6d2147da4b4294ad41398ba1bf4219398eed22b63c1aaa1f8869932e62bc2d5d
Timestamp: 1577853872 Timestamp [UCT]: 2020-01-01 04:44:32 Age [y:d:h:m:s]: 05:074:10:39:50
Block: 36144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203062 RingCT/type: yes/0
Extra: 016d2147da4b4294ad41398ba1bf4219398eed22b63c1aaa1f8869932e62bc2d5d021100000053e39b962a000000000000000000

1 output(s) for total of 465.844290667000 dcy

stealth address amount amount idx
00: f2d69e8c63d274ea1373becf33aa8e2623d93ffb7eddb14ecf4a81a5e7a60c5d 465.844290667000 61134 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": 36154, "vin": [ { "gen": { "height": 36144 } } ], "vout": [ { "amount": 465844290667, "target": { "key": "f2d69e8c63d274ea1373becf33aa8e2623d93ffb7eddb14ecf4a81a5e7a60c5d" } } ], "extra": [ 1, 109, 33, 71, 218, 75, 66, 148, 173, 65, 57, 139, 161, 191, 66, 25, 57, 142, 237, 34, 182, 60, 26, 170, 31, 136, 105, 147, 46, 98, 188, 45, 93, 2, 17, 0, 0, 0, 83, 227, 155, 150, 42, 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