Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ca3f06de90ef71b8055e098d2be2ca03f9fccf1289db8c6ff979e81d07bd970

Tx prefix hash: fdd9c0e536e494f4fd2d278cd96c2e2b5849da13e89524b83b062045f44da138
Tx public key: 068f9bee412ec0977b2afeb78d331e44f5c579f50e443b08ee74bd406ce1d924
Timestamp: 1711861202 Timestamp [UCT]: 2024-03-31 05:00:02 Age [y:d:h:m:s]: 01:223:18:22:42
Block: 990096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418596 RingCT/type: yes/0
Extra: 01068f9bee412ec0977b2afeb78d331e44f5c579f50e443b08ee74bd406ce1d92402110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dde3ad8d7b4a3e9cbc7a836d1a81510c5b085956c2e452af5c35704c1c6bda29 0.600000000000 1450418 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": 990106, "vin": [ { "gen": { "height": 990096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dde3ad8d7b4a3e9cbc7a836d1a81510c5b085956c2e452af5c35704c1c6bda29" } } ], "extra": [ 1, 6, 143, 155, 238, 65, 46, 192, 151, 123, 42, 254, 183, 141, 51, 30, 68, 245, 197, 121, 245, 14, 68, 59, 8, 238, 116, 189, 64, 108, 225, 217, 36, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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