Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c76f7a3bf4156a8d8bff82ef53f478a5989e98ef0d2428cb09667c667fc46169

Tx prefix hash: 14d592f2dcac9cd81ba768a62ed7d2c9cf4974ee9100406e5d67230fab8b6660
Tx public key: 8eab8319056a0469ee9c1b9e59868c10253a03fd6c32ceeee2771371c6f03eea
Timestamp: 1577977175 Timestamp [UCT]: 2020-01-02 14:59:35 Age [y:d:h:m:s]: 05:164:04:38:29
Block: 37293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1267036 RingCT/type: yes/0
Extra: 018eab8319056a0469ee9c1b9e59868c10253a03fd6c32ceeee2771371c6f03eea0211000000428a2ee0d9000000000000000000

1 output(s) for total of 461.778449872000 dcy

stealth address amount amount idx
00: 2fd51e27baec499a4b7cc2c8f4171ae1d11e20dbced0484cf15d8ed7d1ede321 461.778449872000 63247 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": 37303, "vin": [ { "gen": { "height": 37293 } } ], "vout": [ { "amount": 461778449872, "target": { "key": "2fd51e27baec499a4b7cc2c8f4171ae1d11e20dbced0484cf15d8ed7d1ede321" } } ], "extra": [ 1, 142, 171, 131, 25, 5, 106, 4, 105, 238, 156, 27, 158, 89, 134, 140, 16, 37, 58, 3, 253, 108, 50, 206, 238, 226, 119, 19, 113, 198, 240, 62, 234, 2, 17, 0, 0, 0, 66, 138, 46, 224, 217, 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