Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d688f2971b48cc96323721f9aa643bce520acc17a069ce3f04edd96ff03fcbf

Tx prefix hash: 5f7a639202e92ab3ba603a2a84895c4264f3c79523289c3e2c1db452d18091b3
Tx public key: 50ef88663945b8e8e4a6511f05a2948859a8b4990d03363f0cbb3f275a83b34e
Timestamp: 1706845430 Timestamp [UCT]: 2024-02-02 03:43:50 Age [y:d:h:m:s]: 01:027:16:27:43
Block: 948489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280823 RingCT/type: yes/0
Extra: 0150ef88663945b8e8e4a6511f05a2948859a8b4990d03363f0cbb3f275a83b34e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cfefb75090240e4e4cb2f2acf0b3d61ad7eaf97feab1d30396315e76444e4d2 0.600000000000 1406907 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": 948499, "vin": [ { "gen": { "height": 948489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cfefb75090240e4e4cb2f2acf0b3d61ad7eaf97feab1d30396315e76444e4d2" } } ], "extra": [ 1, 80, 239, 136, 102, 57, 69, 184, 232, 228, 166, 81, 31, 5, 162, 148, 136, 89, 168, 180, 153, 13, 3, 54, 63, 12, 187, 63, 39, 90, 131, 179, 78, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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