Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dac12042b81a2b9a53792bdd5bb3bea0b449db8e45211c74299e4ff0e2171c60

Tx prefix hash: 960f8806bbd6ea21b91bc146cabd60be581c75e319c4c34cd7671769fcb3a97b
Tx public key: a9ed7bca3c697fcf82031b48e1d6a313ee7738e4d1b629957317bde5ca030e47
Timestamp: 1713361544 Timestamp [UCT]: 2024-04-17 13:45:44 Age [y:d:h:m:s]: 00:313:16:20:42
Block: 1002513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224224 RingCT/type: yes/0
Extra: 01a9ed7bca3c697fcf82031b48e1d6a313ee7738e4d1b629957317bde5ca030e4702110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb31e115b9dcd8c394af3f2f5e747c318d2b3f621225e34588319461f888a229 0.600000000000 1463029 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": 1002523, "vin": [ { "gen": { "height": 1002513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb31e115b9dcd8c394af3f2f5e747c318d2b3f621225e34588319461f888a229" } } ], "extra": [ 1, 169, 237, 123, 202, 60, 105, 127, 207, 130, 3, 27, 72, 225, 214, 163, 19, 238, 119, 56, 228, 209, 182, 41, 149, 115, 23, 189, 229, 202, 3, 14, 71, 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