Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40170ea543992d73f26c92b25d5bf698a31271e319012b9e3d5d8d909b587aee

Tx prefix hash: 47d36d0bf6f2772577c3142fc25d503f237a61a1015e48ce73e634118d824036
Tx public key: 6c07fad837edcbed217b1baa833ef47c15368cf8999e038b7f4f7c79e1102e39
Timestamp: 1714963330 Timestamp [UCT]: 2024-05-06 02:42:10 Age [y:d:h:m:s]: 00:361:15:39:08
Block: 1015796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258535 RingCT/type: yes/0
Extra: 016c07fad837edcbed217b1baa833ef47c15368cf8999e038b7f4f7c79e1102e3902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d330bf2168a05700e7b95dc92a1f6994571ab503c7f905d9d4984bf7b700afe 0.600000000000 1479239 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": 1015806, "vin": [ { "gen": { "height": 1015796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d330bf2168a05700e7b95dc92a1f6994571ab503c7f905d9d4984bf7b700afe" } } ], "extra": [ 1, 108, 7, 250, 216, 55, 237, 203, 237, 33, 123, 27, 170, 131, 62, 244, 124, 21, 54, 140, 248, 153, 158, 3, 139, 127, 79, 124, 121, 225, 16, 46, 57, 2, 17, 0, 0, 0, 3, 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