Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f53aaa9661883094df160852d884cc07b4389b4a3ebe0465f79ba7ff718eb6

Tx prefix hash: 0c26f29ef84956ea1f798cd5205f1304c964836ca8a38e37972d53de1c5e5786
Tx public key: 4323dc447ea09ab3e5993f3250967fc333e221d12949ca2e3fe2c0b81304a048
Timestamp: 1709058742 Timestamp [UCT]: 2024-02-27 18:32:22 Age [y:d:h:m:s]: 01:109:04:51:48
Block: 966855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339002 RingCT/type: yes/0
Extra: 014323dc447ea09ab3e5993f3250967fc333e221d12949ca2e3fe2c0b81304a0480211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60161abd56b6ff48cbc2cf8ed57cb6303f9b652c0e3a943d00cac099e4f9ea6f 0.600000000000 1426626 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": 966865, "vin": [ { "gen": { "height": 966855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60161abd56b6ff48cbc2cf8ed57cb6303f9b652c0e3a943d00cac099e4f9ea6f" } } ], "extra": [ 1, 67, 35, 220, 68, 126, 160, 154, 179, 229, 153, 63, 50, 80, 150, 127, 195, 51, 226, 33, 209, 41, 73, 202, 46, 63, 226, 192, 184, 19, 4, 160, 72, 2, 17, 0, 0, 0, 9, 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