Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11c0c9337e2524079dcace467c4c2d134045055476b8a639d62acd7ac318a1e1

Tx prefix hash: 8ffe1a939a6260923c3a3a0ab5018aa73e9a1c2cf868de9367f7af50a805ab03
Tx public key: 79d061b4b449ca66a58585f80541b817a0c79b59e25c8f60a99f825787b8b528
Timestamp: 1727598121 Timestamp [UCT]: 2024-09-29 08:22:01 Age [y:d:h:m:s]: 00:167:09:49:31
Block: 1120550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119462 RingCT/type: yes/0
Extra: 0179d061b4b449ca66a58585f80541b817a0c79b59e25c8f60a99f825787b8b52802110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee328fc46734960de163e9258606c6e57b4750f09e04256eec91c1940978e3c5 0.600000000000 1602505 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": 1120560, "vin": [ { "gen": { "height": 1120550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee328fc46734960de163e9258606c6e57b4750f09e04256eec91c1940978e3c5" } } ], "extra": [ 1, 121, 208, 97, 180, 180, 73, 202, 102, 165, 133, 133, 248, 5, 65, 184, 23, 160, 199, 155, 89, 226, 92, 143, 96, 169, 159, 130, 87, 135, 184, 181, 40, 2, 17, 0, 0, 0, 8, 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