Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21bc1883f2e5c93b66688d49ab971722d8c1edefd94cdf1f796489ccfdc3ae06

Tx prefix hash: 467dfab4f37dbca57a0106aac12a81312e6a16965408f319df6cb56e6289ced1
Tx public key: 996d632572671643eca9fed288589e8ab2d52a95e81ae0f2bcf89f4efb29ca9b
Timestamp: 1672641019 Timestamp [UCT]: 2023-01-02 06:30:19 Age [y:d:h:m:s]: 02:131:11:46:37
Block: 665782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 615694 RingCT/type: yes/0
Extra: 01996d632572671643eca9fed288589e8ab2d52a95e81ae0f2bcf89f4efb29ca9b021100000001faf35c9c000000000000000000

1 output(s) for total of 3.819335576000 dcy

stealth address amount amount idx
00: d81214ad36019c4e1002b2bdee15ea98b3e079446f1a47aac40c5159fe9001f2 3.819335576000 1106841 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": 665792, "vin": [ { "gen": { "height": 665782 } } ], "vout": [ { "amount": 3819335576, "target": { "key": "d81214ad36019c4e1002b2bdee15ea98b3e079446f1a47aac40c5159fe9001f2" } } ], "extra": [ 1, 153, 109, 99, 37, 114, 103, 22, 67, 236, 169, 254, 210, 136, 88, 158, 138, 178, 213, 42, 149, 232, 26, 224, 242, 188, 248, 159, 78, 251, 41, 202, 155, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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