Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33e64782915c07cecb2e311f12f8d97d06afac8d655c2707cc8131cac3655af8

Tx prefix hash: 6a7ae50aaa5f05f22438519a4c8fa6563703660589bcc93c15ea2b768383ed4f
Tx public key: c2d859e574148ba90b1441c77f0b9143277deaf4f6875543b6dbcd153961d8af
Timestamp: 1707504119 Timestamp [UCT]: 2024-02-09 18:41:59 Age [y:d:h:m:s]: 01:129:07:35:00
Block: 953950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353405 RingCT/type: yes/0
Extra: 01c2d859e574148ba90b1441c77f0b9143277deaf4f6875543b6dbcd153961d8af02110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03477da7e3e9139fa3098ae2a8be4696e05a8ff7ab2e9c8ea4ce02693b3aa1a7 0.600000000000 1413222 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": 953960, "vin": [ { "gen": { "height": 953950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03477da7e3e9139fa3098ae2a8be4696e05a8ff7ab2e9c8ea4ce02693b3aa1a7" } } ], "extra": [ 1, 194, 216, 89, 229, 116, 20, 139, 169, 11, 20, 65, 199, 127, 11, 145, 67, 39, 125, 234, 244, 246, 135, 85, 67, 182, 219, 205, 21, 57, 97, 216, 175, 2, 17, 0, 0, 0, 13, 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