Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b54c9d6703c98002240a804d409ac5726e55eeb86b1cf20d733440e15e07b08b

Tx prefix hash: 6407f3a59bc23de6df9bea16e0b0901aaed1aa785ca988e88a3c6cfb7482f320
Tx public key: a14494f9add0e80f968a4e2574b39a3f5c3155ea2cffae061b6d4f9f7c209176
Timestamp: 1725882759 Timestamp [UCT]: 2024-09-09 11:52:39 Age [y:d:h:m:s]: 00:121:16:25:55
Block: 1106333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87017 RingCT/type: yes/0
Extra: 01a14494f9add0e80f968a4e2574b39a3f5c3155ea2cffae061b6d4f9f7c20917602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 492221c80cb5d36e0a5cc4485680758f14426b3ae44efaf30caec0328aa54ad0 0.600000000000 1583932 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": 1106343, "vin": [ { "gen": { "height": 1106333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "492221c80cb5d36e0a5cc4485680758f14426b3ae44efaf30caec0328aa54ad0" } } ], "extra": [ 1, 161, 68, 148, 249, 173, 208, 232, 15, 150, 138, 78, 37, 116, 179, 154, 63, 92, 49, 85, 234, 44, 255, 174, 6, 27, 109, 79, 159, 124, 32, 145, 118, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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