Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca0bc5890429f4c38fc1fc39b860111407ac0a89c8854678661ec288bafcf6e6

Tx prefix hash: 781de5840695a8ed57eae6ddd5d8dc63a801e2604604cef219c17130ef42f634
Tx public key: 2a824d72992d125afcb79e57590247b01af2030cd6d3f055c3c0c4baa4ce5d0f
Timestamp: 1734622543 Timestamp [UCT]: 2024-12-19 15:35:43 Age [y:d:h:m:s]: 00:105:20:22:01
Block: 1178699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75412 RingCT/type: yes/0
Extra: 012a824d72992d125afcb79e57590247b01af2030cd6d3f055c3c0c4baa4ce5d0f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fd81f991c1e57c02d2506cc49efca34a459c2f965624da02e49252a0e0d0f20 0.600000000000 1665088 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": 1178709, "vin": [ { "gen": { "height": 1178699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fd81f991c1e57c02d2506cc49efca34a459c2f965624da02e49252a0e0d0f20" } } ], "extra": [ 1, 42, 130, 77, 114, 153, 45, 18, 90, 252, 183, 158, 87, 89, 2, 71, 176, 26, 242, 3, 12, 214, 211, 240, 85, 195, 192, 196, 186, 164, 206, 93, 15, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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