Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93c13a37d5acd37aabc4a042039cf4bb6c10da6065db4d718d066e07256dc1ba

Tx prefix hash: 2b16a14c68d655dd460ab829f9ff480d6de8d5b4b52cc234f0313d460b3b132f
Tx public key: 4b23348ba538f450d57b2c12c56c9c778ff8fe3a02cf9e96e2383965677776fb
Timestamp: 1582514046 Timestamp [UCT]: 2020-02-24 03:14:06 Age [y:d:h:m:s]: 05:081:21:51:27
Block: 71310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1211808 RingCT/type: yes/0
Extra: 014b23348ba538f450d57b2c12c56c9c778ff8fe3a02cf9e96e2383965677776fb021100000001724f989b000000000000000000

1 output(s) for total of 356.222354273000 dcy

stealth address amount amount idx
00: e237a6de148aed61b21a3ad0c7c991747e167e5c0be53d05e159916207cf170e 356.222354273000 131741 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": 71320, "vin": [ { "gen": { "height": 71310 } } ], "vout": [ { "amount": 356222354273, "target": { "key": "e237a6de148aed61b21a3ad0c7c991747e167e5c0be53d05e159916207cf170e" } } ], "extra": [ 1, 75, 35, 52, 139, 165, 56, 244, 80, 213, 123, 44, 18, 197, 108, 156, 119, 143, 248, 254, 58, 2, 207, 158, 150, 226, 56, 57, 101, 103, 119, 118, 251, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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