Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90d0e1e5867996d2abb4ad2b0b524a05b37437d4e882aaecc69dfdde71e18982

Tx prefix hash: 6a2637819ed303dcc32bcbb1069f2816b8c00d469dd435edf4b52913aa897c77
Tx public key: 3131d9e5d93fcf7027455bd4f721369ae64e4eedcd43b15e6b8cc8ad72a32f95
Timestamp: 1675458477 Timestamp [UCT]: 2023-02-03 21:07:57 Age [y:d:h:m:s]: 02:099:04:42:24
Block: 689164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592535 RingCT/type: yes/0
Extra: 013131d9e5d93fcf7027455bd4f721369ae64e4eedcd43b15e6b8cc8ad72a32f950211000000035029cbac000000000000000000

1 output(s) for total of 3.195313774000 dcy

stealth address amount amount idx
00: fa52202eb5a3507a708753ef352ddc4e9dd2d39e5ce9dcf42f00e10a59f9709f 3.195313774000 1131828 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": 689174, "vin": [ { "gen": { "height": 689164 } } ], "vout": [ { "amount": 3195313774, "target": { "key": "fa52202eb5a3507a708753ef352ddc4e9dd2d39e5ce9dcf42f00e10a59f9709f" } } ], "extra": [ 1, 49, 49, 217, 229, 217, 63, 207, 112, 39, 69, 91, 212, 247, 33, 54, 154, 230, 78, 78, 237, 205, 67, 177, 94, 107, 140, 200, 173, 114, 163, 47, 149, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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