Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 761d1b4accb96b67825a15ea532f9926fa27611d8c5f0da83198671266bf1199

Tx prefix hash: a805d06d4973d4d99d9c8d2ae3dc0dd50434dbe3bf7431bc44c93233a842e9ad
Tx public key: 08724d1d2dbbb7eff5a87f98793bc19e82e572e7b68a4dfdf484ce5d5b30441b
Timestamp: 1720975099 Timestamp [UCT]: 2024-07-14 16:38:19 Age [y:d:h:m:s]: 00:277:22:09:11
Block: 1065650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198565 RingCT/type: yes/0
Extra: 0108724d1d2dbbb7eff5a87f98793bc19e82e572e7b68a4dfdf484ce5d5b30441b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aea32a96b2babd64575424dcf72cf1903081fbb468ae36bdd08dfab2e0038e5 0.600000000000 1536199 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": 1065660, "vin": [ { "gen": { "height": 1065650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aea32a96b2babd64575424dcf72cf1903081fbb468ae36bdd08dfab2e0038e5" } } ], "extra": [ 1, 8, 114, 77, 29, 45, 187, 183, 239, 245, 168, 127, 152, 121, 59, 193, 158, 130, 229, 114, 231, 182, 138, 77, 253, 244, 132, 206, 93, 91, 48, 68, 27, 2, 17, 0, 0, 0, 4, 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