Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2844a9cfe04bc5934dfb53be1f3f1558291083978350ea979660e1c123b8284

Tx prefix hash: 6da5c87f4cd3f9b8e97d7e3531f58172761a62655c720f789fcf4c1d53735f14
Tx public key: def14781b0d455213a22941846831662ab0a9db6a16419a4c22140b0f7e1be2a
Timestamp: 1626770081 Timestamp [UCT]: 2021-07-20 08:34:41 Age [y:d:h:m:s]: 03:273:00:46:49
Block: 297470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 966578 RingCT/type: yes/0
Extra: 01def14781b0d455213a22941846831662ab0a9db6a16419a4c22140b0f7e1be2a0211000000d16367b7e9000000000000000000

1 output(s) for total of 63.440475414000 dcy

stealth address amount amount idx
00: 0c2709ababbed1852bec267a261eb196cd7388cd0df0005619604f3b2fd54041 63.440475414000 622578 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": 297480, "vin": [ { "gen": { "height": 297470 } } ], "vout": [ { "amount": 63440475414, "target": { "key": "0c2709ababbed1852bec267a261eb196cd7388cd0df0005619604f3b2fd54041" } } ], "extra": [ 1, 222, 241, 71, 129, 176, 212, 85, 33, 58, 34, 148, 24, 70, 131, 22, 98, 171, 10, 157, 182, 161, 100, 25, 164, 194, 33, 64, 176, 247, 225, 190, 42, 2, 17, 0, 0, 0, 209, 99, 103, 183, 233, 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