Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daeaad63c22cd22b650e6bc3da3007741f842ee68a6ff6bcb5b0e71c911e64f1

Tx prefix hash: f6078752ab2f2601a08e291b7a5cdfe4dbf2968c0b6d8216cadc591fa9fae471
Tx public key: 8bbb6a404f4bfb047c200a673dd5ad73dac7c83e611adab0339d5873be430f96
Timestamp: 1726788589 Timestamp [UCT]: 2024-09-19 23:29:49 Age [y:d:h:m:s]: 01:051:00:17:31
Block: 1113836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294866 RingCT/type: yes/0
Extra: 018bbb6a404f4bfb047c200a673dd5ad73dac7c83e611adab0339d5873be430f9602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebf7f7ff426f1a2a3ad7cdc040112dd045ea2b67ea4a530efa3cad42ff779055 0.600000000000 1593633 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": 1113846, "vin": [ { "gen": { "height": 1113836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebf7f7ff426f1a2a3ad7cdc040112dd045ea2b67ea4a530efa3cad42ff779055" } } ], "extra": [ 1, 139, 187, 106, 64, 79, 75, 251, 4, 124, 32, 10, 103, 61, 213, 173, 115, 218, 199, 200, 62, 97, 26, 218, 176, 51, 157, 88, 115, 190, 67, 15, 150, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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