Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2c3aa0ad2f5b6d7e960dabf0ca8ac66d492846349b345ab8d577d421e1d6b89

Tx prefix hash: a27c07a043eb9f2da4aab98e4e845fd16a64c0e2865498f58bf5cb1aa0419efe
Tx public key: 7b296af1f3cb82f9342d410bbdcbc5388713604935a04631a3158a3a563410f9
Timestamp: 1696842805 Timestamp [UCT]: 2023-10-09 09:13:25 Age [y:d:h:m:s]: 01:095:11:32:53
Block: 865783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329480 RingCT/type: yes/0
Extra: 017b296af1f3cb82f9342d410bbdcbc5388713604935a04631a3158a3a563410f902110000000133af99f4000000000000000000

1 output(s) for total of 0.830427172000 dcy

stealth address amount amount idx
00: 6b239e020c9df51113f829cb8799cac6d6a654d7e0b647bcc0ec5b45291c8f38 0.830427172000 1320331 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": 865793, "vin": [ { "gen": { "height": 865783 } } ], "vout": [ { "amount": 830427172, "target": { "key": "6b239e020c9df51113f829cb8799cac6d6a654d7e0b647bcc0ec5b45291c8f38" } } ], "extra": [ 1, 123, 41, 106, 241, 243, 203, 130, 249, 52, 45, 65, 11, 189, 203, 197, 56, 135, 19, 96, 73, 53, 160, 70, 49, 163, 21, 138, 58, 86, 52, 16, 249, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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