Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8392e9c431dd78f5f73e510fe0bf881526579e8d629174190e82b923109c44f2

Tx prefix hash: 3a0e441f70e15b214ccf0f9536c1293a20ac6ee3ae0e9b09d1e25344aa11742d
Tx public key: 5a7a8754495a625a6d7a6072e25db8eb582117bd5b9460b8e9969cafbe3e4e5c
Timestamp: 1631667636 Timestamp [UCT]: 2021-09-15 01:00:36 Age [y:d:h:m:s]: 03:173:08:31:28
Block: 333987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899315 RingCT/type: yes/0
Extra: 015a7a8754495a625a6d7a6072e25db8eb582117bd5b9460b8e9969cafbe3e4e5c0211000000215410958b000000000000000000

1 output(s) for total of 48.017004675000 dcy

stealth address amount amount idx
00: 02c80441cb426a925a6a74d4cfd0b9bae3a22660b84d0a9f3eaa4f251217809b 48.017004675000 689028 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": 333997, "vin": [ { "gen": { "height": 333987 } } ], "vout": [ { "amount": 48017004675, "target": { "key": "02c80441cb426a925a6a74d4cfd0b9bae3a22660b84d0a9f3eaa4f251217809b" } } ], "extra": [ 1, 90, 122, 135, 84, 73, 90, 98, 90, 109, 122, 96, 114, 226, 93, 184, 235, 88, 33, 23, 189, 91, 148, 96, 184, 233, 150, 156, 175, 190, 62, 78, 92, 2, 17, 0, 0, 0, 33, 84, 16, 149, 139, 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