Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0be1deeb4a5a063bd732f80b9b0b341bb53e8fa2b7824f8657b89fa43c996ae5

Tx prefix hash: 91eab25c763ab8793d7acf2a095076ebd2af60ca076779c6f3868a7154237896
Tx public key: 0f9acc0eaf80d7a81aeadeb34292f6b5dd7d6a2a79658a9ded583ec6cc156055
Timestamp: 1713944214 Timestamp [UCT]: 2024-04-24 07:36:54 Age [y:d:h:m:s]: 00:349:11:50:55
Block: 1007350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249831 RingCT/type: yes/0
Extra: 010f9acc0eaf80d7a81aeadeb34292f6b5dd7d6a2a79658a9ded583ec6cc15605502110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea95320ba4af19e971462f8d878a74b8beeedcf045a54fbe92f6f862185cd4c8 0.600000000000 1468664 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": 1007360, "vin": [ { "gen": { "height": 1007350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea95320ba4af19e971462f8d878a74b8beeedcf045a54fbe92f6f862185cd4c8" } } ], "extra": [ 1, 15, 154, 204, 14, 175, 128, 215, 168, 26, 234, 222, 179, 66, 146, 246, 181, 221, 125, 106, 42, 121, 101, 138, 157, 237, 88, 62, 198, 204, 21, 96, 85, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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