Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0783c3a57ba7ff96d1b752e93aaaa1231d033f55893c20d72935d2e79a1c1f08

Tx prefix hash: e1335027e284404051e0f121ae22cd3caaa7c80ea06b751892cc300e350694f9
Tx public key: e9f14252ef4900dc73557b40781cd1b06c981d01b91b938207c6facc31d6b153
Timestamp: 1698812715 Timestamp [UCT]: 2023-11-01 04:25:15 Age [y:d:h:m:s]: 01:089:18:41:08
Block: 882108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325135 RingCT/type: yes/0
Extra: 01e9f14252ef4900dc73557b40781cd1b06c981d01b91b938207c6facc31d6b15302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.733179013000 dcy

stealth address amount amount idx
00: 0374a499c2f48cd2a8eff970226d12f35fcb0532e1f0ddda7ab2cd537d0ea348 0.733179013000 1337746 of 0

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": 882118, "vin": [ { "gen": { "height": 882108 } } ], "vout": [ { "amount": 733179013, "target": { "key": "0374a499c2f48cd2a8eff970226d12f35fcb0532e1f0ddda7ab2cd537d0ea348" } } ], "extra": [ 1, 233, 241, 66, 82, 239, 73, 0, 220, 115, 85, 123, 64, 120, 28, 209, 176, 108, 152, 29, 1, 185, 27, 147, 130, 7, 198, 250, 204, 49, 214, 177, 83, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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