Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c945dab5c84df0f36070331ca16907edc13f4ead1f948ab46372cde044b1e76

Tx prefix hash: bfb9487b05b35a2f2d4b55732bdfd9a3d95da5305874375bfb200bcb379dc8b1
Tx public key: 5513f3588a1026a2b650c5ced3fd2a3eada9e112347cf8ca3c7a08614be4671b
Timestamp: 1736980311 Timestamp [UCT]: 2025-01-15 22:31:51 Age [y:d:h:m:s]: 00:303:01:05:15
Block: 1198178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214097 RingCT/type: yes/0
Extra: 015513f3588a1026a2b650c5ced3fd2a3eada9e112347cf8ca3c7a08614be4671b0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 022a9c4d070c38029e3aeca9295bba94f95b40def4548d5e5de7cca75ef289aa 0.600000000000 1684797 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": 1198188, "vin": [ { "gen": { "height": 1198178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "022a9c4d070c38029e3aeca9295bba94f95b40def4548d5e5de7cca75ef289aa" } } ], "extra": [ 1, 85, 19, 243, 88, 138, 16, 38, 162, 182, 80, 197, 206, 211, 253, 42, 62, 173, 169, 225, 18, 52, 124, 248, 202, 60, 122, 8, 97, 75, 228, 103, 27, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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