Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e549f1de6b63835571e5c28cab90e7f1e476ca752da9670b1d0b3a976875f981

Tx prefix hash: 6fc91366019ecd807fa5ac2f243bdd310e137a8df92f256c3e69dffd79e494ca
Tx public key: ba625b9d427b5da482e9a3e44f7c85d0c044f4a8702491b2a2f8f92354cd77d3
Timestamp: 1720819307 Timestamp [UCT]: 2024-07-12 21:21:47 Age [y:d:h:m:s]: 00:247:14:52:22
Block: 1064357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176907 RingCT/type: yes/0
Extra: 01ba625b9d427b5da482e9a3e44f7c85d0c044f4a8702491b2a2f8f92354cd77d302110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42706f66e4e41aa8f752b9455451b833dd6399e787eac8df2e7a16c345ba33c5 0.600000000000 1534882 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": 1064367, "vin": [ { "gen": { "height": 1064357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42706f66e4e41aa8f752b9455451b833dd6399e787eac8df2e7a16c345ba33c5" } } ], "extra": [ 1, 186, 98, 91, 157, 66, 123, 93, 164, 130, 233, 163, 228, 79, 124, 133, 208, 192, 68, 244, 168, 112, 36, 145, 178, 162, 248, 249, 35, 84, 205, 119, 211, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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