Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c394bfd3e0e6e802e66451839344adbc815a50b434afbd6b3ec639b9efc28e69

Tx prefix hash: 4b01d732262ac175af9f63485619fb66c140e1a3f03f82e8448e690cddc03390
Tx public key: 37d7030b17882d48a3fbacdb9a3ea262eae68067cfa7f1a85225020522315c00
Timestamp: 1694719405 Timestamp [UCT]: 2023-09-14 19:23:25 Age [y:d:h:m:s]: 01:131:01:37:11
Block: 848151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354950 RingCT/type: yes/0
Extra: 0137d7030b17882d48a3fbacdb9a3ea262eae68067cfa7f1a85225020522315c0002110000000175e3f0e9000000000000000000

1 output(s) for total of 0.950000234000 dcy

stealth address amount amount idx
00: 6afdc8a3f7c26d747bf14eee0aff3beabed736c33db5cce99a747f4318cd8dcc 0.950000234000 1301737 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": 848161, "vin": [ { "gen": { "height": 848151 } } ], "vout": [ { "amount": 950000234, "target": { "key": "6afdc8a3f7c26d747bf14eee0aff3beabed736c33db5cce99a747f4318cd8dcc" } } ], "extra": [ 1, 55, 215, 3, 11, 23, 136, 45, 72, 163, 251, 172, 219, 154, 62, 162, 98, 234, 230, 128, 103, 207, 167, 241, 168, 82, 37, 2, 5, 34, 49, 92, 0, 2, 17, 0, 0, 0, 1, 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