Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7dfa8b85febf64e05964e0c66dc9bf14a87eacf3389ebf4cd00e8729bc8eb1

Tx prefix hash: 183f2111f0678c8f37b24b2d53905c8de3a662769e3c4f5a6f5679d4992b74f6
Tx public key: 99678946cc4322ccbe565229d5cf333d220e17a7af5faeaf8fb10d4faff5275c
Timestamp: 1710696867 Timestamp [UCT]: 2024-03-17 17:34:27 Age [y:d:h:m:s]: 00:187:17:18:03
Block: 980446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134448 RingCT/type: yes/0
Extra: 0199678946cc4322ccbe565229d5cf333d220e17a7af5faeaf8fb10d4faff5275c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05b6083fd2d2f957ea7e4f0b1ccc42e3853f10f9eadc2cbc917db243266198a1 0.600000000000 1440513 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": 980456, "vin": [ { "gen": { "height": 980446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05b6083fd2d2f957ea7e4f0b1ccc42e3853f10f9eadc2cbc917db243266198a1" } } ], "extra": [ 1, 153, 103, 137, 70, 204, 67, 34, 204, 190, 86, 82, 41, 213, 207, 51, 61, 34, 14, 23, 167, 175, 95, 174, 175, 143, 177, 13, 79, 175, 245, 39, 92, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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