Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abeb336ba9baa5f803b9ec6b5bf8e09cc350532e6e36ef738663c3a062bb74b6

Tx prefix hash: 9406ae2e87d31d0850a64fb0e3a9854facb83fbf8d07fa49cd355df96c5b47ee
Tx public key: 30bfd597ecb3870f20370db21c7c63d64c5cf835c9f3711ce048d6bbdf789129
Timestamp: 1728450046 Timestamp [UCT]: 2024-10-09 05:00:46 Age [y:d:h:m:s]: 00:175:23:43:45
Block: 1127612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125559 RingCT/type: yes/0
Extra: 0130bfd597ecb3870f20370db21c7c63d64c5cf835c9f3711ce048d6bbdf78912902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deef3b40239eeb82d0487517d67b4cb65c5da3d724b822d49aac2a7394e175a9 0.600000000000 1610419 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": 1127622, "vin": [ { "gen": { "height": 1127612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deef3b40239eeb82d0487517d67b4cb65c5da3d724b822d49aac2a7394e175a9" } } ], "extra": [ 1, 48, 191, 213, 151, 236, 179, 135, 15, 32, 55, 13, 178, 28, 124, 99, 214, 76, 92, 248, 53, 201, 243, 113, 28, 224, 72, 214, 187, 223, 120, 145, 41, 2, 17, 0, 0, 0, 1, 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