Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81373ada294b079e49c45881bd35492afaf567aac6430542a32e967299f813e0

Tx prefix hash: ca740a1e4a56724a2ccfe3c516eb148e313c22df9af07e2bd320a2518999bca8
Tx public key: b047322cb2980be7ff4104ff05639a53e1f6fa1ff09f5b2a1ac848a595442435
Timestamp: 1695639108 Timestamp [UCT]: 2023-09-25 10:51:48 Age [y:d:h:m:s]: 01:185:21:40:41
Block: 855787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393927 RingCT/type: yes/0
Extra: 01b047322cb2980be7ff4104ff05639a53e1f6fa1ff09f5b2a1ac848a59544243502110000000975e3f0e9000000000000000000

1 output(s) for total of 0.896236162000 dcy

stealth address amount amount idx
00: 2b2e0a9e235b4eb121c5b92a3303d5d54eed1a44e16c534407525b383538b8ac 0.896236162000 1309829 of 0

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": 855797, "vin": [ { "gen": { "height": 855787 } } ], "vout": [ { "amount": 896236162, "target": { "key": "2b2e0a9e235b4eb121c5b92a3303d5d54eed1a44e16c534407525b383538b8ac" } } ], "extra": [ 1, 176, 71, 50, 44, 178, 152, 11, 231, 255, 65, 4, 255, 5, 99, 154, 83, 225, 246, 250, 31, 240, 159, 91, 42, 26, 200, 72, 165, 149, 68, 36, 53, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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