Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56470e50edb95aa54d39d071da350e158ce083c11fc194b69653d50c3372b556

Tx prefix hash: cbfad72e7985a139ec31cb7c64a651aa396d96a4b786238a3e1553f8bb65faab
Tx public key: 3084c96428ccf3da5ae24eae5a72aa2f42d026f28118f90c877d85fa1b35e24e
Timestamp: 1717294174 Timestamp [UCT]: 2024-06-02 02:09:34 Age [y:d:h:m:s]: 00:223:23:43:12
Block: 1035126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160294 RingCT/type: yes/0
Extra: 013084c96428ccf3da5ae24eae5a72aa2f42d026f28118f90c877d85fa1b35e24e021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffd41fc1df6284922ef54ef7516fd9859aac683889d9ae6ad6930e1f55b7c35c 0.600000000000 1503645 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": 1035136, "vin": [ { "gen": { "height": 1035126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffd41fc1df6284922ef54ef7516fd9859aac683889d9ae6ad6930e1f55b7c35c" } } ], "extra": [ 1, 48, 132, 201, 100, 40, 204, 243, 218, 90, 226, 78, 174, 90, 114, 170, 47, 66, 208, 38, 242, 129, 24, 249, 12, 135, 125, 133, 250, 27, 53, 226, 78, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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