Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a18f3cd8d68ac1dd2d9fb99dd7312731b2fb6dfa639af24a1fa9e4e0000d77dd

Tx prefix hash: 2529914038a0fa6d67b310295db067b442f3e4aa00465093dd9e5bd143422f3e
Tx public key: 07cd902902d11ea907ec53abc4ee9ff0b4aabe5cc5ed338b3872264e2090d66e
Timestamp: 1725458191 Timestamp [UCT]: 2024-09-04 13:56:31 Age [y:d:h:m:s]: 00:081:08:52:28
Block: 1102817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58182 RingCT/type: yes/0
Extra: 0107cd902902d11ea907ec53abc4ee9ff0b4aabe5cc5ed338b3872264e2090d66e02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e530d884a6743b7ba64ee93aeb286a8dc057715b08e1df4a0c266163471ff5b 0.600000000000 1579396 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": 1102827, "vin": [ { "gen": { "height": 1102817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e530d884a6743b7ba64ee93aeb286a8dc057715b08e1df4a0c266163471ff5b" } } ], "extra": [ 1, 7, 205, 144, 41, 2, 209, 30, 169, 7, 236, 83, 171, 196, 238, 159, 240, 180, 170, 190, 92, 197, 237, 51, 139, 56, 114, 38, 78, 32, 144, 214, 110, 2, 17, 0, 0, 0, 10, 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