Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caebde222bb57dbc6459a255fc9a59896f6bbfd598861920d3b874275e852a8d

Tx prefix hash: aa3ac3930f3f0c577a5f75827057ca799996a1ab0310c6bb442c8a809d1220d3
Tx public key: db7d8554d8dab7bd1077d7be8b1a34ad5338b6364aa7d3f1775e80019e14f7e8
Timestamp: 1745889316 Timestamp [UCT]: 2025-04-29 01:15:16 Age [y:d:h:m:s]: 00:251:00:17:09
Block: 1271676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177180 RingCT/type: yes/0
Extra: 01db7d8554d8dab7bd1077d7be8b1a34ad5338b6364aa7d3f1775e80019e14f7e80211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ff01a0f90c8571dde6b0aae647624c2063d41d692d7476a1708cfbfd6e18dd1 0.600000000000 1758943 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": 1271686, "vin": [ { "gen": { "height": 1271676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ff01a0f90c8571dde6b0aae647624c2063d41d692d7476a1708cfbfd6e18dd1" } } ], "extra": [ 1, 219, 125, 133, 84, 216, 218, 183, 189, 16, 119, 215, 190, 139, 26, 52, 173, 83, 56, 182, 54, 74, 167, 211, 241, 119, 94, 128, 1, 158, 20, 247, 232, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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