Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac06f66bd67f70596544545dfceeaa94c4de486ea431935cc5faf739f6892c8

Tx prefix hash: 6a6898033565d94e40a674ba41a37b33bc968d82d497965c0f11ab8f06f00e08
Tx public key: 17bee06f6c8b91772a44a6008a8e79bc330730720042a7d7b20ecc24afc8e59f
Timestamp: 1749618673 Timestamp [UCT]: 2025-06-11 05:11:13 Age [y:d:h:m:s]: 00:152:14:34:29
Block: 1302539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106759 RingCT/type: yes/0
Extra: 0117bee06f6c8b91772a44a6008a8e79bc330730720042a7d7b20ecc24afc8e59f021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 952658c95e27aa82bf2b8d4b39815ae88a234b9424045c3df81cc9c78ee8d3a5 0.600000000000 1790110 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": 1302549, "vin": [ { "gen": { "height": 1302539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "952658c95e27aa82bf2b8d4b39815ae88a234b9424045c3df81cc9c78ee8d3a5" } } ], "extra": [ 1, 23, 190, 224, 111, 108, 139, 145, 119, 42, 68, 166, 0, 138, 142, 121, 188, 51, 7, 48, 114, 0, 66, 167, 215, 178, 14, 204, 36, 175, 200, 229, 159, 2, 17, 0, 0, 0, 5, 228, 220, 144, 9, 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