Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 271876689126a38ebcadd931c1496628cacf7850c1f3781ed6f18b4ec9bf71b8

Tx prefix hash: b10a145be25f1fa2a225361ded51b581eb2aaa3602d4bd3155412f911937f5c3
Tx public key: a1a5d7a71daaa1c70d8e73f929a14ecf08b22ae89d48699168b94d6ff1038dd5
Timestamp: 1670894793 Timestamp [UCT]: 2022-12-13 01:26:33 Age [y:d:h:m:s]: 02:332:11:28:35
Block: 651345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 757030 RingCT/type: yes/0
Extra: 01a1a5d7a71daaa1c70d8e73f929a14ecf08b22ae89d48699168b94d6ff1038dd50211000000037e406890000000000000000000

1 output(s) for total of 4.264063008000 dcy

stealth address amount amount idx
00: 12a80390910e06ac0d8f5ebc4e5b33a58c01597d5c80791158db2ec31cbaf216 4.264063008000 1091752 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": 651355, "vin": [ { "gen": { "height": 651345 } } ], "vout": [ { "amount": 4264063008, "target": { "key": "12a80390910e06ac0d8f5ebc4e5b33a58c01597d5c80791158db2ec31cbaf216" } } ], "extra": [ 1, 161, 165, 215, 167, 29, 170, 161, 199, 13, 142, 115, 249, 41, 161, 78, 207, 8, 178, 42, 232, 157, 72, 105, 145, 104, 185, 77, 111, 241, 3, 141, 213, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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