Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b791c49a756a1757fad03f175dff796f63d61cfe16408d26f9ee462e6a0cc0

Tx prefix hash: 0930493172d32e8978c1a7a50f168e8580011bd8896088451363beaacf15c3ba
Tx public key: 5481a6bf56a7e38e1eec2f89d03d3e3e86a3cab3e0ab4514043c36fe70958162
Timestamp: 1716736866 Timestamp [UCT]: 2024-05-26 15:21:06 Age [y:d:h:m:s]: 00:316:02:18:23
Block: 1030516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225895 RingCT/type: yes/0
Extra: 015481a6bf56a7e38e1eec2f89d03d3e3e86a3cab3e0ab4514043c36fe7095816202110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc22e85f10e3d4b410411b1e2f69f14905d357a5bd8fab0c5f99a1062f77f136 0.600000000000 1498771 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": 1030526, "vin": [ { "gen": { "height": 1030516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc22e85f10e3d4b410411b1e2f69f14905d357a5bd8fab0c5f99a1062f77f136" } } ], "extra": [ 1, 84, 129, 166, 191, 86, 167, 227, 142, 30, 236, 47, 137, 208, 61, 62, 62, 134, 163, 202, 179, 224, 171, 69, 20, 4, 60, 54, 254, 112, 149, 129, 98, 2, 17, 0, 0, 0, 5, 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