Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d67b3d1c2e22be12088878f38ae07d8e6b353be91e5b09ff05bb091f7ddbfc79

Tx prefix hash: de998884f6b8fd7896ce3b92aa8cc22b16e9486cec7be171d79e55a4d3ce8994
Tx public key: a3a5233c6669a48ca1361a4e4d73984fa523a137c31a9f472b0a13fe9417ab76
Timestamp: 1746569525 Timestamp [UCT]: 2025-05-06 22:12:05 Age [y:d:h:m:s]: 00:154:06:51:39
Block: 1277300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107918 RingCT/type: yes/0
Extra: 01a3a5233c6669a48ca1361a4e4d73984fa523a137c31a9f472b0a13fe9417ab760211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcfc179ace44bf24d3eb2bae95ca1cf597c8d43b1470844a14cebc64e6d1aa4f 0.600000000000 1764655 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": 1277310, "vin": [ { "gen": { "height": 1277300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcfc179ace44bf24d3eb2bae95ca1cf597c8d43b1470844a14cebc64e6d1aa4f" } } ], "extra": [ 1, 163, 165, 35, 60, 102, 105, 164, 140, 161, 54, 26, 78, 77, 115, 152, 79, 165, 35, 161, 55, 195, 26, 159, 71, 43, 10, 19, 254, 148, 23, 171, 118, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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