Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ea0261784f857fc65bf88f7829767917ab0d2010d68dde8bdb8315947af708b

Tx prefix hash: cfe00f0d447c8bab2eb90e5d109643618000b7fbefb2516fb8932d1bb0ab9e7d
Tx public key: 65c9ec7de6579bc6d03fea7d74cc94021db781f2e515dd064f5b1f7ca7eb0097
Timestamp: 1730652451 Timestamp [UCT]: 2024-11-03 16:47:31 Age [y:d:h:m:s]: 00:024:21:40:57
Block: 1145786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17831 RingCT/type: yes/0
Extra: 0165c9ec7de6579bc6d03fea7d74cc94021db781f2e515dd064f5b1f7ca7eb0097021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c660429190990dbd3cc805a47a761902cb3a25a48d03fb249eb1d4719a06714 0.600000000000 1630295 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": 1145796, "vin": [ { "gen": { "height": 1145786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c660429190990dbd3cc805a47a761902cb3a25a48d03fb249eb1d4719a06714" } } ], "extra": [ 1, 101, 201, 236, 125, 230, 87, 155, 198, 208, 63, 234, 125, 116, 204, 148, 2, 29, 183, 129, 242, 229, 21, 221, 6, 79, 91, 31, 124, 167, 235, 0, 151, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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