Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b446201bfa4c02ce58d0b6cab81d6034cd2dbba7e48a4d73cabfc51dcf83ca35

Tx prefix hash: 6ac0f6e97bb25f270c6ad34c0dddb72c12b7a54b7f32d3d194552ea435190cb7
Tx public key: bd53c5fe224795dbfdb5366323bcff252e957526970ef00ca9b9f0f2a4572f6a
Timestamp: 1709736597 Timestamp [UCT]: 2024-03-06 14:49:57 Age [y:d:h:m:s]: 01:012:19:56:50
Block: 972477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270178 RingCT/type: yes/0
Extra: 01bd53c5fe224795dbfdb5366323bcff252e957526970ef00ca9b9f0f2a4572f6a02110000000246812bb8000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8638e6008d4d972bcb5ae2f7f36aac4f4f5e116331bab0c05515fdaccc1a9221 0.600000000000 1432392 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": 972487, "vin": [ { "gen": { "height": 972477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8638e6008d4d972bcb5ae2f7f36aac4f4f5e116331bab0c05515fdaccc1a9221" } } ], "extra": [ 1, 189, 83, 197, 254, 34, 71, 149, 219, 253, 181, 54, 99, 35, 188, 255, 37, 46, 149, 117, 38, 151, 14, 240, 12, 169, 185, 240, 242, 164, 87, 47, 106, 2, 17, 0, 0, 0, 2, 70, 129, 43, 184, 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