Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7072596a4176e37d1c984c3e18b67bb8487808e95274e8973eb3d8fec979b076

Tx prefix hash: a34a850e7a5b2a07ab3689105bf969f2b7a46a60709f5a4abae4bc4c48bbbb6b
Tx public key: 2e5918f50e497f6928f194533ae1e6269ebdc97e9810b6d8c022e8754ae821a9
Timestamp: 1680211711 Timestamp [UCT]: 2023-03-30 21:28:31 Age [y:d:h:m:s]: 02:008:21:20:57
Block: 728597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527851 RingCT/type: yes/0
Extra: 012e5918f50e497f6928f194533ae1e6269ebdc97e9810b6d8c022e8754ae821a90211000000045029cbac000000000000000000

1 output(s) for total of 2.365134910000 dcy

stealth address amount amount idx
00: c0fbb3f8055e85205519b82393f0e15e542ecd8393f304dc21cba9305858d73d 2.365134910000 1174014 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": 728607, "vin": [ { "gen": { "height": 728597 } } ], "vout": [ { "amount": 2365134910, "target": { "key": "c0fbb3f8055e85205519b82393f0e15e542ecd8393f304dc21cba9305858d73d" } } ], "extra": [ 1, 46, 89, 24, 245, 14, 73, 127, 105, 40, 241, 148, 83, 58, 225, 230, 38, 158, 189, 201, 126, 152, 16, 182, 216, 192, 34, 232, 117, 74, 232, 33, 169, 2, 17, 0, 0, 0, 4, 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