Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f86d8657b1ac53a4f2c25981774dc7df865b251302a1a4b4ea23a58a1265d7be

Tx prefix hash: fe68310b66565a8bf500361c99104edaa6af89895dd5ed56224c32f2542bf76f
Tx public key: 6ffa9c3982b0998d2b9659dddcb72cb04f29301afe7c7591b141a0e5207650c0
Timestamp: 1703021173 Timestamp [UCT]: 2023-12-19 21:26:13 Age [y:d:h:m:s]: 01:039:21:46:10
Block: 916796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289630 RingCT/type: yes/0
Extra: 016ffa9c3982b0998d2b9659dddcb72cb04f29301afe7c7591b141a0e5207650c0021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6b000f0e4e22df2506973f34645f50e9771b6c4af59af4cb4e46d69fd910784 0.600000000000 1374356 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": 916806, "vin": [ { "gen": { "height": 916796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6b000f0e4e22df2506973f34645f50e9771b6c4af59af4cb4e46d69fd910784" } } ], "extra": [ 1, 111, 250, 156, 57, 130, 176, 153, 141, 43, 150, 89, 221, 220, 183, 44, 176, 79, 41, 48, 26, 254, 124, 117, 145, 177, 65, 160, 229, 32, 118, 80, 192, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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