Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 349098607a9687c5827260778d5cb2476c41b2a4d61382f63b6d7497abacabb8

Tx prefix hash: 05f645e3c420bf7c78c1a8bed36ceeac0032d70a51cf102e30944e0e579e8564
Tx public key: 3e88719d148df8e577f367a0aae71a5c70c67d2571eab356eaf1703f1c36b4e8
Timestamp: 1749363682 Timestamp [UCT]: 2025-06-08 06:21:22 Age [y:d:h:m:s]: 00:158:23:46:08
Block: 1300449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111306 RingCT/type: yes/0
Extra: 013e88719d148df8e577f367a0aae71a5c70c67d2571eab356eaf1703f1c36b4e8021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27a6fe01745565c817561d1b2554272fd890a16c6593766d5e3eae9d85a1e1d4 0.600000000000 1787998 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": 1300459, "vin": [ { "gen": { "height": 1300449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27a6fe01745565c817561d1b2554272fd890a16c6593766d5e3eae9d85a1e1d4" } } ], "extra": [ 1, 62, 136, 113, 157, 20, 141, 248, 229, 119, 243, 103, 160, 170, 231, 26, 92, 112, 198, 125, 37, 113, 234, 179, 86, 234, 241, 112, 63, 28, 54, 180, 232, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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