Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfda9e82cd409b9c12cf5f241794b7475b4cde80f19d7977b0fb39262d122248

Tx prefix hash: 02ef58e5d8daeaa7e410947d13907cc514165b4fc8604dfa62d30e829ffbb103
Tx public key: e01634a818e4a12a017572e70332cdf0d9e53afd6362bf056f1a4f71365b4a8f
Timestamp: 1714011761 Timestamp [UCT]: 2024-04-25 02:22:41 Age [y:d:h:m:s]: 01:053:19:08:16
Block: 1007899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299308 RingCT/type: yes/0
Extra: 01e01634a818e4a12a017572e70332cdf0d9e53afd6362bf056f1a4f71365b4a8f02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9b252e38699e68c6057dd7fc3573cf92adcfd932b694992c56bf12b425ec5f7 0.600000000000 1469365 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": 1007909, "vin": [ { "gen": { "height": 1007899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9b252e38699e68c6057dd7fc3573cf92adcfd932b694992c56bf12b425ec5f7" } } ], "extra": [ 1, 224, 22, 52, 168, 24, 228, 161, 42, 1, 117, 114, 231, 3, 50, 205, 240, 217, 229, 58, 253, 99, 98, 191, 5, 111, 26, 79, 113, 54, 91, 74, 143, 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