Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a2e242ba2adcfc699b67504eeda93fc0436a1c24b472f5e61f1f405b920f390

Tx prefix hash: 546e7d6acf5e3bd0551cd3e759fe6d6cc80ead16f6912c0255a26ebac769aa1a
Tx public key: 60794a746d4cf26af15e91728f4313ec6caab772b36afd8f8ad95e3255b3d389
Timestamp: 1711718584 Timestamp [UCT]: 2024-03-29 13:23:04 Age [y:d:h:m:s]: 01:019:15:42:19
Block: 988921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274998 RingCT/type: yes/0
Extra: 0160794a746d4cf26af15e91728f4313ec6caab772b36afd8f8ad95e3255b3d38902110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fb89777341be77bde5dad9cac6bdd264d916d23d0ac173f2f611ae12303e9bb 0.600000000000 1449210 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": 988931, "vin": [ { "gen": { "height": 988921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fb89777341be77bde5dad9cac6bdd264d916d23d0ac173f2f611ae12303e9bb" } } ], "extra": [ 1, 96, 121, 74, 116, 109, 76, 242, 106, 241, 94, 145, 114, 143, 67, 19, 236, 108, 170, 183, 114, 179, 106, 253, 143, 138, 217, 94, 50, 85, 179, 211, 137, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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