Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ded425af664e4671a00d0e8e3aded08b8f3dc9d5f29790dde143f811c126311

Tx prefix hash: 5ffc6d50b710d07f119e4424f58b9bfd44cb3219c5e92cc4aac8150bc41b35b6
Tx public key: 0cd71e8b5c2e39969685f93d48d56b5916fcf6d64dd14ea18bc62a1720b52463
Timestamp: 1707007122 Timestamp [UCT]: 2024-02-04 00:38:42 Age [y:d:h:m:s]: 01:024:05:52:11
Block: 949822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278359 RingCT/type: yes/0
Extra: 010cd71e8b5c2e39969685f93d48d56b5916fcf6d64dd14ea18bc62a1720b5246302110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db852b92ea62b34f375bece3ae51f45cdf50c885195327254ed16c625e1b1f58 0.600000000000 1408354 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": 949832, "vin": [ { "gen": { "height": 949822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db852b92ea62b34f375bece3ae51f45cdf50c885195327254ed16c625e1b1f58" } } ], "extra": [ 1, 12, 215, 30, 139, 92, 46, 57, 150, 150, 133, 249, 61, 72, 213, 107, 89, 22, 252, 246, 214, 77, 209, 78, 161, 139, 198, 42, 23, 32, 181, 36, 99, 2, 17, 0, 0, 0, 9, 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