Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fd2fd1cbda5bd1b610c665f7f3c88de29edbe0b5d61b9b294c4e35415c1f4d9

Tx prefix hash: 3bc8f9f55cab69f38aaa24acacf47814554cc9ebf1b017e8a10ecc4993df739d
Tx public key: bdfa50e3caae6fd3bff13aa684be185628596ca6aac2da4596cffaf6f5f20480
Timestamp: 1703806981 Timestamp [UCT]: 2023-12-28 23:43:01 Age [y:d:h:m:s]: 01:091:08:07:24
Block: 923305 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326385 RingCT/type: yes/0
Extra: 01bdfa50e3caae6fd3bff13aa684be185628596ca6aac2da4596cffaf6f5f204800211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 824e665b8e591b856e7c6bfd9c18b9295be851e23169c634c1e7c1def36ca49d 0.600000000000 1381033 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": 923315, "vin": [ { "gen": { "height": 923305 } } ], "vout": [ { "amount": 600000000, "target": { "key": "824e665b8e591b856e7c6bfd9c18b9295be851e23169c634c1e7c1def36ca49d" } } ], "extra": [ 1, 189, 250, 80, 227, 202, 174, 111, 211, 191, 241, 58, 166, 132, 190, 24, 86, 40, 89, 108, 166, 170, 194, 218, 69, 150, 207, 250, 246, 245, 242, 4, 128, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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