Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1c24436fe10567d78e84dd0b4adc77f2e753d8af609b26992dd047dc42e6bd1

Tx prefix hash: e5a1e2f57fa874d007ac77b7d7a14daa4643450a3b9902b5693c8ca4be52ad8d
Tx public key: ab84d5bcccaafaebaa93c4746b01f69889595d2a9429b51f202bad8b333a16c9
Timestamp: 1676420534 Timestamp [UCT]: 2023-02-15 00:22:14 Age [y:d:h:m:s]: 02:011:10:57:39
Block: 697148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 529752 RingCT/type: yes/0
Extra: 01ab84d5bcccaafaebaa93c4746b01f69889595d2a9429b51f202bad8b333a16c9021100000002835e4d22000000000000000000

1 output(s) for total of 3.006486053000 dcy

stealth address amount amount idx
00: 1a3f992ac24968a82073f73ae73279207ffb0f6f7a4bcbc54597e9ccdd78bfe8 3.006486053000 1140259 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": 697158, "vin": [ { "gen": { "height": 697148 } } ], "vout": [ { "amount": 3006486053, "target": { "key": "1a3f992ac24968a82073f73ae73279207ffb0f6f7a4bcbc54597e9ccdd78bfe8" } } ], "extra": [ 1, 171, 132, 213, 188, 204, 170, 250, 235, 170, 147, 196, 116, 107, 1, 246, 152, 137, 89, 93, 42, 148, 41, 181, 31, 32, 43, 173, 139, 51, 58, 22, 201, 2, 17, 0, 0, 0, 2, 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