Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be61b91dec7d5344254cfb1063b856a08097c19a5438e90f230ab47a2f5cd822

Tx prefix hash: d7bc92bdd8c1719a6a463797682cfd6672f98d0472c90c2cb196b5d4b60971df
Tx public key: 0df8a90ea40f4a4a225e870fe3320a3090302e9efbd2a410f3be03bcf82cfacf
Timestamp: 1718022486 Timestamp [UCT]: 2024-06-10 12:28:06 Age [y:d:h:m:s]: 01:149:04:09:25
Block: 1041166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365159 RingCT/type: yes/0
Extra: 010df8a90ea40f4a4a225e870fe3320a3090302e9efbd2a410f3be03bcf82cfacf0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ca0dedf4002171b910a94249536fc46d06eac4c56a1b16c8a2d998704332ff1 0.600000000000 1509831 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": 1041176, "vin": [ { "gen": { "height": 1041166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ca0dedf4002171b910a94249536fc46d06eac4c56a1b16c8a2d998704332ff1" } } ], "extra": [ 1, 13, 248, 169, 14, 164, 15, 74, 74, 34, 94, 135, 15, 227, 50, 10, 48, 144, 48, 46, 158, 251, 210, 164, 16, 243, 190, 3, 188, 248, 44, 250, 207, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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