Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 798e9c3fca563108c163572ba19114663c8935ecea0b6d430a229d2bf745401a

Tx prefix hash: 1c7732ea5d73c575800ba906b3f84ab6380f6a79bf253d01ae3bd2438ed4fedc
Tx public key: 0d37179ff63ab1c4cbda1c782d7338beb85936699e2aa94d5ab6949bdc48f966
Timestamp: 1735135874 Timestamp [UCT]: 2024-12-25 14:11:14 Age [y:d:h:m:s]: 00:086:11:05:09
Block: 1182925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61571 RingCT/type: yes/0
Extra: 010d37179ff63ab1c4cbda1c782d7338beb85936699e2aa94d5ab6949bdc48f9660211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70d1f783fd16af2122f78c0b3c5ca32def18a4a8d6cf984c12489a64bc12dd44 0.600000000000 1669364 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": 1182935, "vin": [ { "gen": { "height": 1182925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70d1f783fd16af2122f78c0b3c5ca32def18a4a8d6cf984c12489a64bc12dd44" } } ], "extra": [ 1, 13, 55, 23, 159, 246, 58, 177, 196, 203, 218, 28, 120, 45, 115, 56, 190, 184, 89, 54, 105, 158, 42, 169, 77, 90, 182, 148, 155, 220, 72, 249, 102, 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