Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41ed246723b85ed373c36bc38450e3d9cb9692e8571998e1f29c17204639766d

Tx prefix hash: fa10e7323c21e4e526c991813334c5e89837ae85cc9f17ea4f60ebfda5e6f021
Tx public key: e594ca646fa0e85c903e5fac021b2aabc42f786d6dbfc466b85cc20c7d13f0e5
Timestamp: 1576643430 Timestamp [UCT]: 2019-12-18 04:30:30 Age [y:d:h:m:s]: 04:323:23:52:07
Block: 28214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118623 RingCT/type: yes/0
Extra: 01e594ca646fa0e85c903e5fac021b2aabc42f786d6dbfc466b85cc20c7d13f0e502110000001cad433a0b000000000000000000

1 output(s) for total of 494.898537849000 dcy

stealth address amount amount idx
00: 4257f88bb11ba3ce5bf91977c9673eca5c6f9a443415a40dda133d397b1ca36a 494.898537849000 46744 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": 28224, "vin": [ { "gen": { "height": 28214 } } ], "vout": [ { "amount": 494898537849, "target": { "key": "4257f88bb11ba3ce5bf91977c9673eca5c6f9a443415a40dda133d397b1ca36a" } } ], "extra": [ 1, 229, 148, 202, 100, 111, 160, 232, 92, 144, 62, 95, 172, 2, 27, 42, 171, 196, 47, 120, 109, 109, 191, 196, 102, 184, 92, 194, 12, 125, 19, 240, 229, 2, 17, 0, 0, 0, 28, 173, 67, 58, 11, 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