Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 793d959e6168da4445e51f921459b27ded024962f09c08c727bfa283f1d9148b

Tx prefix hash: 919206440721617540954d06598697b11e91092bf97ee9cd7d12fa9c334228dc
Tx public key: 973f108b14778072e2f2e0b731df86fb9e60912a0d86036911c6852e6e29952b
Timestamp: 1676591361 Timestamp [UCT]: 2023-02-16 23:49:21 Age [y:d:h:m:s]: 01:347:00:18:52
Block: 698561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508717 RingCT/type: yes/0
Extra: 01973f108b14778072e2f2e0b731df86fb9e60912a0d86036911c6852e6e29952b021100000006835e4d22000000000000000000

1 output(s) for total of 2.974249080000 dcy

stealth address amount amount idx
00: b03f83e90c89be15e151c2463a6a6bc0eb281b15b35d0f3efc973cacb4718ce1 2.974249080000 1141870 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": 698571, "vin": [ { "gen": { "height": 698561 } } ], "vout": [ { "amount": 2974249080, "target": { "key": "b03f83e90c89be15e151c2463a6a6bc0eb281b15b35d0f3efc973cacb4718ce1" } } ], "extra": [ 1, 151, 63, 16, 139, 20, 119, 128, 114, 226, 242, 224, 183, 49, 223, 134, 251, 158, 96, 145, 42, 13, 134, 3, 105, 17, 198, 133, 46, 110, 41, 149, 43, 2, 17, 0, 0, 0, 6, 131, 94, 77, 34, 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