Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 067cabe7d671d0f7374e5a6817b87d3ba30895c7a89ea22a4e4067d043a129ab

Tx prefix hash: c58e1ea9ccb1bf8315984f4f0f692942e92d6221e4d818646b093d3f336479d0
Tx public key: 877a1ab518527a15878ee1a5f8f92d7db244ca00cc450eca5344e3ee28370e44
Timestamp: 1750613437 Timestamp [UCT]: 2025-06-22 17:30:37 Age [y:d:h:m:s]: 00:151:12:33:13
Block: 1310590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106156 RingCT/type: yes/0
Extra: 01877a1ab518527a15878ee1a5f8f92d7db244ca00cc450eca5344e3ee28370e440211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7a9ba8e279cfcaed5811f7d80d8f8dd2a2b39d8d94e5b1de82236136136ba4 0.600000000000 1798211 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": 1310600, "vin": [ { "gen": { "height": 1310590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7a9ba8e279cfcaed5811f7d80d8f8dd2a2b39d8d94e5b1de82236136136ba4" } } ], "extra": [ 1, 135, 122, 26, 181, 24, 82, 122, 21, 135, 142, 225, 165, 248, 249, 45, 125, 178, 68, 202, 0, 204, 69, 14, 202, 83, 68, 227, 238, 40, 55, 14, 68, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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