Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ecabc91598b650d94b5b5f0d32ed34d905ce77dc5d6541a1a1d54f6ca29bd17

Tx prefix hash: 9e130c0a9bc115f923ffb107c4aefa6ba924a7f5b7b8b03acf4399c3eaf17be6
Tx public key: 3bd766f0d9c15ac29fec1c2486879e4299e5e9bafe031015549021fb2a33c906
Timestamp: 1706063273 Timestamp [UCT]: 2024-01-24 02:27:53 Age [y:d:h:m:s]: 01:070:06:14:52
Block: 941983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311310 RingCT/type: yes/0
Extra: 013bd766f0d9c15ac29fec1c2486879e4299e5e9bafe031015549021fb2a33c90602110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2776d7ea17bafad4cefa9bb194e840d06561d486a1a2e05154038b191ce69168 0.600000000000 1400147 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": 941993, "vin": [ { "gen": { "height": 941983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2776d7ea17bafad4cefa9bb194e840d06561d486a1a2e05154038b191ce69168" } } ], "extra": [ 1, 59, 215, 102, 240, 217, 193, 90, 194, 159, 236, 28, 36, 134, 135, 158, 66, 153, 229, 233, 186, 254, 3, 16, 21, 84, 144, 33, 251, 42, 51, 201, 6, 2, 17, 0, 0, 0, 13, 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