Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef6b77143e569889f4e2752d49a5ebaa9aa07b0fca22849f3f7ec2fb1797b566

Tx prefix hash: 3c0500f9c1b3c7939b149b447458456247819fa3cf50b0f6dc70edd4a7c34fbe
Tx public key: e819bca57fa5ba21d4f21d34081dbbfbc3bdbe5efd1d163fb823bb9d884cf08f
Timestamp: 1745779666 Timestamp [UCT]: 2025-04-27 18:47:46 Age [y:d:h:m:s]: 00:010:12:18:10
Block: 1270764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7518 RingCT/type: yes/0
Extra: 01e819bca57fa5ba21d4f21d34081dbbfbc3bdbe5efd1d163fb823bb9d884cf08f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46ed5e2b499112ba64ae326983de10cbc58009dafc1d2de08b60c373daa299e4 0.600000000000 1758009 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": 1270774, "vin": [ { "gen": { "height": 1270764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46ed5e2b499112ba64ae326983de10cbc58009dafc1d2de08b60c373daa299e4" } } ], "extra": [ 1, 232, 25, 188, 165, 127, 165, 186, 33, 212, 242, 29, 52, 8, 29, 187, 251, 195, 189, 190, 94, 253, 29, 22, 63, 184, 35, 187, 157, 136, 76, 240, 143, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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