Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d5de41634ce189bc37da274eb2028882adec5f4cd5c31026cf4bf3909a01ca2

Tx prefix hash: 1d77aeeb5cb0952d6d70aa10ac189c5799aa0ece967f9d25ce63eac90f17e0e1
Tx public key: 8d22af38b370a19ce8d74135932b82f08aa76bae423d6e85886934a40716a59b
Timestamp: 1695743963 Timestamp [UCT]: 2023-09-26 15:59:23 Age [y:d:h:m:s]: 01:191:22:04:56
Block: 856661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398221 RingCT/type: yes/0
Extra: 018d22af38b370a19ce8d74135932b82f08aa76bae423d6e85886934a40716a59b021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.890279836000 dcy

stealth address amount amount idx
00: 1c601d2eb9d302e271038ee1dc635e1ea4a03504f1ced33a6c1946d8c20e622e 0.890279836000 1310743 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": 856671, "vin": [ { "gen": { "height": 856661 } } ], "vout": [ { "amount": 890279836, "target": { "key": "1c601d2eb9d302e271038ee1dc635e1ea4a03504f1ced33a6c1946d8c20e622e" } } ], "extra": [ 1, 141, 34, 175, 56, 179, 112, 161, 156, 232, 215, 65, 53, 147, 43, 130, 240, 138, 167, 107, 174, 66, 61, 110, 133, 136, 105, 52, 164, 7, 22, 165, 155, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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