Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b585f1f10688617d2454e329e52039875b14e35c23bce61c9ca3ebecb055f813

Tx prefix hash: 634a2b8f6ed8d343c80d1ff67fb206d346b6d367f06c4c5af7e43600fa9a7f23
Tx public key: 6c63715523eedaf06a61b22c8eac4d0a6ce898d6119b5056c6c0293ef3bf331d
Timestamp: 1711091815 Timestamp [UCT]: 2024-03-22 07:16:55 Age [y:d:h:m:s]: 00:255:13:29:02
Block: 983722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182953 RingCT/type: yes/0
Extra: 016c63715523eedaf06a61b22c8eac4d0a6ce898d6119b5056c6c0293ef3bf331d02110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0043111e4f657fb35fde7db4b5a4c579c381ebad8765660dfdecc464bdc575e 0.600000000000 1443863 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": 983732, "vin": [ { "gen": { "height": 983722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0043111e4f657fb35fde7db4b5a4c579c381ebad8765660dfdecc464bdc575e" } } ], "extra": [ 1, 108, 99, 113, 85, 35, 238, 218, 240, 106, 97, 178, 44, 142, 172, 77, 10, 108, 232, 152, 214, 17, 155, 80, 86, 198, 192, 41, 62, 243, 191, 51, 29, 2, 17, 0, 0, 0, 14, 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