Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be19d3626848859a7bbf8fe794d55bc43ff51ee6186b42f0c7427f73385c70e3

Tx prefix hash: 665f126b03079a45fc0af39f778e38fd9bfcf65c99e5f0782c21152ee54cef6f
Tx public key: 276a43646d7846935c0aaf4e7b4bcf8c7972630a7c2560faaa0d8e4d5747c3dd
Timestamp: 1737961620 Timestamp [UCT]: 2025-01-27 07:07:00 Age [y:d:h:m:s]: 00:141:17:42:51
Block: 1206081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101221 RingCT/type: yes/0
Extra: 01276a43646d7846935c0aaf4e7b4bcf8c7972630a7c2560faaa0d8e4d5747c3dd0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34993ab03ad2f05ff36fd87c72335bbcc69e31f218afa8af87c94b34db98e2aa 0.600000000000 1692782 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": 1206091, "vin": [ { "gen": { "height": 1206081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34993ab03ad2f05ff36fd87c72335bbcc69e31f218afa8af87c94b34db98e2aa" } } ], "extra": [ 1, 39, 106, 67, 100, 109, 120, 70, 147, 92, 10, 175, 78, 123, 75, 207, 140, 121, 114, 99, 10, 124, 37, 96, 250, 170, 13, 142, 77, 87, 71, 195, 221, 2, 17, 0, 0, 0, 2, 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