Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d4169ff387dccaa26b2445bd19e8e51aceae4f28006ca65b5fb8adbe35a91fc

Tx prefix hash: 743c6e032a735e1183a1a1e6445ade54732dfa95d7f5ae6af97512f2fc566e83
Tx public key: 4a5ffe60ccb62a97e9287ac3d4c63fe529ee76abc45e61079f3fab1e9a87744c
Timestamp: 1716053118 Timestamp [UCT]: 2024-05-18 17:25:18 Age [y:d:h:m:s]: 00:321:19:31:24
Block: 1024834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230021 RingCT/type: yes/0
Extra: 014a5ffe60ccb62a97e9287ac3d4c63fe529ee76abc45e61079f3fab1e9a87744c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 825b7448ba0593f123e32cb5c9874045a53553e3a55ca430f9e09adce1e706c2 0.600000000000 1490887 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": 1024844, "vin": [ { "gen": { "height": 1024834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "825b7448ba0593f123e32cb5c9874045a53553e3a55ca430f9e09adce1e706c2" } } ], "extra": [ 1, 74, 95, 254, 96, 204, 182, 42, 151, 233, 40, 122, 195, 212, 198, 63, 229, 41, 238, 118, 171, 196, 94, 97, 7, 159, 63, 171, 30, 154, 135, 116, 76, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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