Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0780cfd584366288937b690db28b0aaa49bb891fce1d6d6cb34fecfdefef236

Tx prefix hash: 40227fda1f582ebcd6a64ce536be9b3e6da96ce54c2178f6631c9e94057e421f
Tx public key: 1e579a93a8082f7e7bddcd70fca776bd7a3fc4fa57ae45cf089e6417e9578a23
Timestamp: 1581652375 Timestamp [UCT]: 2020-02-14 03:52:55 Age [y:d:h:m:s]: 04:318:14:26:26
Block: 64626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119837 RingCT/type: yes/0
Extra: 011e579a93a8082f7e7bddcd70fca776bd7a3fc4fa57ae45cf089e6417e9578a230211000000234943cd9f000000000000000000

1 output(s) for total of 374.859089533000 dcy

stealth address amount amount idx
00: 287c650333fee7fa2143a2090edc5b73bf03041934e20025d71ac7d197b18123 374.859089533000 119206 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": 64636, "vin": [ { "gen": { "height": 64626 } } ], "vout": [ { "amount": 374859089533, "target": { "key": "287c650333fee7fa2143a2090edc5b73bf03041934e20025d71ac7d197b18123" } } ], "extra": [ 1, 30, 87, 154, 147, 168, 8, 47, 126, 123, 221, 205, 112, 252, 167, 118, 189, 122, 63, 196, 250, 87, 174, 69, 207, 8, 158, 100, 23, 233, 87, 138, 35, 2, 17, 0, 0, 0, 35, 73, 67, 205, 159, 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