Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 670ea82373e2e3288cf7633bd9234cb2a4ffc0593d2bfcce4c5ad9d7eccee603

Tx prefix hash: 7a8d0201aac0a2ebad1c1b1d11f31e352b7ee19340c03eaecc347222c55439f3
Tx public key: 417a7c4c6df2e862a596d7487b1b9303c0d164d381c45a867472c97c932cd69b
Timestamp: 1710481815 Timestamp [UCT]: 2024-03-15 05:50:15 Age [y:d:h:m:s]: 01:024:12:43:26
Block: 978660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278498 RingCT/type: yes/0
Extra: 01417a7c4c6df2e862a596d7487b1b9303c0d164d381c45a867472c97c932cd69b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9dde8f4cb5025429598720bea2f7dddcf2e49666b9aed021a963a9ede918de2 0.600000000000 1438689 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": 978670, "vin": [ { "gen": { "height": 978660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9dde8f4cb5025429598720bea2f7dddcf2e49666b9aed021a963a9ede918de2" } } ], "extra": [ 1, 65, 122, 124, 76, 109, 242, 232, 98, 165, 150, 215, 72, 123, 27, 147, 3, 192, 209, 100, 211, 129, 196, 90, 134, 116, 114, 201, 124, 147, 44, 214, 155, 2, 17, 0, 0, 0, 1, 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