Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fc23e723df2bdef1b44023e71e1d037a3359150021b2e6114e53a129db0e7a6

Tx prefix hash: e5bca933ce4602f710ca7a737847d138bf6de8de9da8200f1867273f636fae04
Tx public key: 150a20caa13d64c2fdeea6078b42b6a18f7377b997b59d6f08cc9e887e49abe3
Timestamp: 1704728728 Timestamp [UCT]: 2024-01-08 15:45:28 Age [y:d:h:m:s]: 01:303:13:14:48
Block: 930935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475772 RingCT/type: yes/0
Extra: 01150a20caa13d64c2fdeea6078b42b6a18f7377b997b59d6f08cc9e887e49abe302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bcdfa8c78a243f57c747a4a04f3391530e9e7288791ce3b1efacce0e79434f0 0.600000000000 1388825 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": 930945, "vin": [ { "gen": { "height": 930935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bcdfa8c78a243f57c747a4a04f3391530e9e7288791ce3b1efacce0e79434f0" } } ], "extra": [ 1, 21, 10, 32, 202, 161, 61, 100, 194, 253, 238, 166, 7, 139, 66, 182, 161, 143, 115, 119, 185, 151, 181, 157, 111, 8, 204, 158, 136, 126, 73, 171, 227, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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