Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0978339cbe94a0c10affd2a49730cefdabf53266567e29ac9544fd7bfc1b1373

Tx prefix hash: e2d4efc2fab58bf51d0f1d51a52a3992d54b7f2794cb80215b7686f84cd68bdc
Tx public key: 7a4c055cedc5e2927eed2fc9e98ad481039b9493d1717c91e1fb18882e93f02d
Timestamp: 1710108530 Timestamp [UCT]: 2024-03-10 22:08:50 Age [y:d:h:m:s]: 01:066:16:13:25
Block: 975553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308673 RingCT/type: yes/0
Extra: 017a4c055cedc5e2927eed2fc9e98ad481039b9493d1717c91e1fb18882e93f02d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd74ca747e826947872cc10e6df16ca3cfda2a179a0bfc9e5f236a79f5260054 0.600000000000 1435526 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": 975563, "vin": [ { "gen": { "height": 975553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd74ca747e826947872cc10e6df16ca3cfda2a179a0bfc9e5f236a79f5260054" } } ], "extra": [ 1, 122, 76, 5, 92, 237, 197, 226, 146, 126, 237, 47, 201, 233, 138, 212, 129, 3, 155, 148, 147, 209, 113, 124, 145, 225, 251, 24, 136, 46, 147, 240, 45, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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