Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8090d4985411cbcd269f5d88e17a7b3231e4f3fd6a4de44554452beed505fee

Tx prefix hash: 71e2b3d43381e7e6dba87f569bbd569386be286d443f2e1a567b4992df531d38
Tx public key: 9c767b71fe7f530f3cd9e8e8ab1f4f636b89fe722e987c2f94d0a36915d278fa
Timestamp: 1722722756 Timestamp [UCT]: 2024-08-03 22:05:56 Age [y:d:h:m:s]: 00:242:15:21:46
Block: 1080126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173312 RingCT/type: yes/0
Extra: 019c767b71fe7f530f3cd9e8e8ab1f4f636b89fe722e987c2f94d0a36915d278fa021100000018e914dd15000000000000000000

1 output(s) for total of 0.615620000000 dcy

stealth address amount amount idx
00: a8f5874e2ad557868bd84e4a70ccc5507e154d392700bc2a27dbcabb6d61770a 0.615620000000 1553367 of 0

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": 1080136, "vin": [ { "gen": { "height": 1080126 } } ], "vout": [ { "amount": 615620000, "target": { "key": "a8f5874e2ad557868bd84e4a70ccc5507e154d392700bc2a27dbcabb6d61770a" } } ], "extra": [ 1, 156, 118, 123, 113, 254, 127, 83, 15, 60, 217, 232, 232, 171, 31, 79, 99, 107, 137, 254, 114, 46, 152, 124, 47, 148, 208, 163, 105, 21, 210, 120, 250, 2, 17, 0, 0, 0, 24, 233, 20, 221, 21, 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